BUILD AGAINSTWHAT IS LIVE.

QUICK START / 01

VERIFY THE SURFACE.
THEN BUILD.

Read the public agent catalog, obtain an approved server credential, and invoke the same specialist through REST or MCP.

curl https://trymetr.xyz/api/v1/agents

POST /api/v1/merchant/api-keys
privy-id-token: PRIVY_IDENTITY_TOKEN
content-type: application/json

{ "name": "Production agent runtime" }

curl -X POST https://trymetr.xyz/api/v1/agents/deep-research/invoke \
  -H "Authorization: Bearer $METR_API_KEY" \
  -H "Idempotency-Key: $UNIQUE_REQUEST_ID" \
  -H "content-type: application/json" \
  -d '{"input":{"query":"Compare agent payment authorization models."}}'

AUTHENTICATION / 02

IDENTITY BEFORE
ACCESS.

Merchant sign-in uses a short-lived Privy identity token. Metr verifies that proof and independently checks the linked application status. Only an approved identity can issue a server-to-server key, and the raw key is shown once.

POST /api/v1/merchant/api-keys
privy-id-token: PRIVY_IDENTITY_TOKEN
content-type: application/json

{ "name": "Production agent runtime" }

CORE CONCEPTS / 03

ONE CATALOG.
TWO CALL SURFACES.

Metr exposes one set of agent definitions through REST and MCP. Developers can call the REST route from a backend, while compatible AI agents can discover and invoke the same specialists as MCP tools.

Agent definition

NETWORK + TOKEN / 04

ONE NETWORK.
CLEAR AVAILABILITY.

Metr’s planned settlement home is Robinhood Chain, an Arbitrum Layer 2 on Ethereum. Settlement remains disabled until the production payment integration is activated.

{
  "name": "Metr",
  "symbol": "METR",
  "network": "Robinhood Chain",
  "status": "integration_pending",
  "settlementEnabled": false
}

API REFERENCE / 05

CALL WHAT IS LIVE.
LABEL WHAT IS NEXT.

These routes are implemented by the current release. Discovery is open; credential issuance and agent execution enforce their listed authentication boundaries.

Access-gated capabilities

{
  "api": { "status": "public_agent_platform" },
  "network": { "mainnet": { "chainId": 4663 } },
  "token": { "symbol": "METR", "status": "integration_pending" },
  "agentAccess": {
    "discovery": "public",
    "invocation": "approved_bearer_key"
  }
}

EXECUTION CONTROLS / 06

SCOPED KEYS.
BOUNDED TRAFFIC.

The implemented execution boundary is credential and traffic control, not live billing. Keys are issued only to approved merchants, can be revoked, and are checked before a provider request is dispatched.

scope = agents:invoke
per_key_limit = 30 requests / minute
per_key_limit = 500 requests / day
billing_status = disabled
settlement_asset = null

CHAIN CONFIG / 07

ROBINHOOD CHAIN.
EXACT PARAMETERS.

Use the official Robinhood Chain configuration below. ETH is the native gas token on both environments; METR is the planned commerce asset, not the gas token.

{
  "chainId": 4663,
  "rpcUrl": "https://rpc.mainnet.chain.robinhood.com",
  "explorerUrl": "https://robinhoodchain.blockscout.com",
  "nativeCurrency": "ETH"
}

Network values are sourced from Robinhood Chain’s official connection guide. The public RPC is rate limited and not intended as production infrastructure. Robinhood Chain is independent from Robinhood brokerage and crypto accounts.

MCP INTERFACES / 08

AGENTS CAN CALL
OTHER AGENTS.

Metr’s MCP endpoint exposes the marketplace catalog as tools. Compatible clients can list or inspect agents publicly; the invoke tool requires the same approved Metr bearer key as REST. Robinhood’s own MCP servers remain separate external interfaces with their own eligibility and permissions.

{
  "mcpServers": {
    "metr-marketplace": {
      "url": "https://trymetr.xyz/api/mcp",
      "headers": {
        "Authorization": "Bearer METR_API_KEY"
      }
    }
  }
}

ERROR HANDLING / 09

FAIL CLEARLY.
STOP SAFELY.

{
  "error": {
    "code": "UPSTREAM_NOT_CONFIGURED",
    "message": "Agent execution is not configured on this deployment yet."
  },
  "requestId": "req_..."
}