Build Autonomous Workflows
The Bidda Agentic SDKs allow your LLM agents, LangChain bots, and autonomous workflows to programmatically consume our source-verified intelligence library.
Discovery API
Access the /api/v1/nodes/index.json endpoint for real-time registry discovery, or use the tool in the Forest.
Base EVM Settlement
Native x402 enforcement on the Cloudflare Edge. Pay 0.01 USDC on Base to unlock vaults.
Integrity Proofs
Every node includes a SHA-256 hash to ensure provenance and truth-verification.
Implementation Quickstart
Select your agentic environment
// Install via CDN or local import
import BiddaClient from './sdk/bidda-agent-sdk.js';
const agent = new BiddaClient({
baseUrl: 'https://bidda.com'
});
// 1. Discover available intelligence
const registry = await agent.discover();
console.log(`Found ${registry.total_nodes} nodes`);
// 2. Initialize and verify a specific node
const node = await agent.initializeNode('iso-42001-risk-assess');
console.log(node.workflow);CLI & Agentic Native Fetch
Your agents don't need our interface. They can discover the forest metadata for free via the Discovery API, and hit the vault completely headless by submitting a Base USDC transaction hash as their L402 proof.
Protocol: Decentralized x402
1. Discovery Call (Metadata - Free)
curl -G https://bidda.com/api/v1/nodes/iso-42001.json
Returns title, authority, version, and BLUF. Ideal for agent indexing and task planning.
2. Payload Call (Gated Intelligence - $0.01 USDC)
# Cloudflare Edge Block (Returns 402):
curl -G https://bidda.com/api/v1/vault/iso-42001.json
# With Web3 x402 Validated TxHash:
curl -G https://bidda.com/api/v1/vault/iso-42001.json \
-H "Authorization: L402 web3:token:0xValidBaseTxHash..."
Returns the full deterministic workflow, machine-readable schema, and primary citations.
Under The Hood: Why is it secure?
Our system relies on physical Cloudflare Edge Architecture. When you pass your transaction's hash to our endpoints, our edge server executes an instantaneous JSON-RPC verification call to the live Base network. It cryptographically verifies that your transaction occurred, that it perfectly matched the required 0.01 USDC transfer (`0x2710` hex payload), and that you routed it to our exact Treasury wallet identifier.
Diagnostics Matrix
| Symptom | Diagnosis | Resolution Path |
|---|---|---|
| HTTP 402 Return (Despite Hash) | The transaction hash was invalid, or RPC indexing latency occurred. | Wait 30 seconds for Blockchain indexing, then retry the API call with the exact same hash. Do not rebuild the transaction. |
| "Verification Failed" Response | The transaction succeeded, but the transfer logic did not match 0.01 USDC exactly to our treasury. | Verify your web3 scripts are passing EXACTLY 0.01 into the token transfer parameter on Base. |
| Missing L402 Authorization Header | Your autonomous agent attempted to fetch the payload without completing the preamble. | Programmatically parse the HTTP 402 object to retrieve the dynamic invoice payload before fetching. |
API Response Schemas
Public Metadata (Discovery)
{
"id": "iso-42001-risk",
"title": "ISO/IEC 42001 AI Risk Assessment",
"authority": "ISO (International Standard)",
"bluf": "Structured framework for assessing AI risks...",
"verification": {
"source_url": "https://iso.org/...",
"hash": "sha256-8a2f..."
}
}Vault Intelligence (GATED)
{
"id": "iso-42001-risk",
"actionable_schema": {
"maximum_latency_ms": 200,
"failover_trigger": "EVENT_ID_408",
"required_human_loop": ["bias_threshold_breach", "capital_flight > $10,000"]
},
"deterministic_workflow": [
{ "step": 1, "logic": "If input == PII, force boundary filter to AES-256 state." },
{ "step": 2, "logic": "Compute risk coefficient. If (R > 0.85), halt agent process." }
],
"primary_citations": ["ISO 42001 Annex A.4.2", "NIST AI RMF 1.0 (MAP 1.5)"]
}Ready for Production?
Combine Bidda's source-verified intelligence with live payment infrastructure to build the next generation of autonomous B2B services. 777 nodes are ready for integration today.
v1.2.5 — 2026-04-12