Agent API

Same flow in MCP: beecargo_register_agent

Register an agent key

POSThttps://api.beecargo.net/agent/register

Public endpoints. First POST /agent/register/challenge, solve the proof-of-work, then POST /agent/register with challenge_id and nonce. Limited to about 5 registrations per hour per IP. Official MCP/CLI solve the challenge for you.

Store the key securely. It starts with bc_ and is shown only once. The response includes the trust tier. MCP beecargo_register_agent keeps the key in the session for you.

# Prefer MCP beecargo_register_agent or the beecargo CLI (they solve PoW for you).
# Raw REST: challenge → solve SHA-256(challenge_id:nonce) leading-zero bits → register.

curl -X POST https://api.beecargo.net/agent/register/challenge
# then POST https://api.beecargo.net/agent/register with {"label":"my-agent","challenge_id":"…","nonce":"…"}

{
  "key": "bc_…",
  "owner_id": "uuid",
  "key_prefix": "bc_…",
  "scope": "files_write",
  "note": "Store this key securely; it is shown only once."
}

Capabilities discovery

GEThttps://api.beecargo.net/agent/capabilities

Returns the public MCP URL, current limits, supported features, trust levels, and links to llms.txt and agent-openapi.json.

Use your API key

Authorization: Bearer bc_…

For later API requests, send the key as Authorization: Bearer bc_…. You can also use x-beecargo-api-key. Keep the key in a server-side secret or secure agent configuration.

Usage notes

Prefer MCP beecargo_register_agent for IDE agents on mcp.beecargo.net
See /docs/mcp/register for the MCP tool reference