Connect an AgentAgent Quickstart

Agent Quickstart

1. Create an API key

Create a key at conyr.ai/api. The same Bearer key authenticates REST, WebSocket, and the hosted MCP server.

2. Connect the agent

MCP is the shortest path to the full intelligence catalog:

claude mcp add --transport http conyr https://mcp.conyr.ai/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Ask the connected agent:

Use Conyr's token_deep_dive tool on <MINT>. Separate observed facts from missing sections and include the evidence URL.

The four composite tools are token_deep_dive, token_coordination_report, wallet_overview, and wallet_network_report. Use a focused query_* tool when the task needs only one primitive.

3. Or call REST directly

All /v1/* operations use the production base URL https://api.conyr.ai and require Authorization: Bearer <API_KEY>.

curl -sS \
  -H "Authorization: Bearer YOUR_API_KEY" \
  "https://api.conyr.ai/v1/token/MINT/bundles/summary"

Response

{
  "token_mint": "MINT",
  "bundle_count": 3,
  "open_bundle_count": 2,
  "bundled_supply_pct": 0.142,
  "bundled_value_usd": 28400.0,
  "bundled_realized_pnl_usd": 6100.0,
  "dominant_bundle_type": "SyntheticSwarm"
}

4. Handle absence and failure separately

REST errors use this envelope:

{"error": "Human-readable description", "code": 400}

An HTTP 200 with null, an empty array, or a response containing unknown fields is not an error. Preserve those states so the agent does not turn “not observed” into “safe.” Composite MCP tools make source failures explicit with partial and errors.

⚠️

WebSocket is authenticated too. Native browser WebSocket cannot attach an arbitrary Authorization header; connect from an agent backend or an approved proxy that can send the Bearer header.

Next steps