API model (A2A)

BizBionic is not a classic multi-path REST product for new features. Integrators call named skills through one endpoint.

The one door

POST https://app.bizbionic.com/rpc
Content-Type: application/json
Authorization: Bearer bb_…

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "billing.balance",
  "params": {}
}

Success:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": { }
}

Error:

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32602,
    "message": "…",
    "data": { "next_actions": [] }
  }
}

Discovery

curl -s https://app.bizbionic.com/.well-known/agent.json

Returns skills list, RPC URL, auth hints, partner workflows, and documentation links.

OpenAPI catalog

We publish an OpenAPI catalog of every A2A skill for search and tooling. Paths like /a2a/campaigns.list in that file are documentation-only — production traffic always hits /rpc.

What stays the same for humans and agents

Consent, quiet hours, credits, brand/Trust gates — cx-parity. UI and agents call the same skill registry.

​API model (A2A)

​The one door

​Discovery

​OpenAPI catalog

​What stays the same for humans and agents

​Next steps

API model (A2A)

The one door

Discovery

OpenAPI catalog

What stays the same for humans and agents

Next steps