API Overview

Every capability described in What Protos Can Do is available over one endpoint. This is exactly what powers Protos’s own iMessage integration today.

The endpoint

curl -sX POST /api/chat \
  -H "Content-Type: application/json" \
  -d '{"message":"who is buying $pepe","format":"text","anonId":"chat-123"}'

{
  "type": "intel",
  "text": "$PEPE — top buyers: Wintermute Market Making +$10.69M, … Net accumulating $15.54M."
}

Set format:"text" and you get a plain-text answer back instead of a UI card. No SDK, no API key, no card-shape knowledge required — relay the text field verbatim and you have a working bot.

Request fields

Field	Description
`message`	Required. The user’s text, verbatim.
`format`	`"text"` \| `"card"` — default `"card"`. The browser uses `"card"`; headless clients send `"text"`.
`anonId`	Required for text-mode intel reads — a stable per-conversation id that drives the cost cap.
`senderAddress`	Optional. A connected wallet unlocks that address’s tier.
`sparkline`	Optional, default `true` — set `false` to omit the ASCII price chart.

Response fields

Field	Description
`type`	The card type — branch on it if you want, or ignore it entirely.
`text`	Always populated, plain text, ready to relay as-is.
`link`	On swap / bridge / pay replies — a tap-to-sign URL. Protos is non-custodial, so execution always finishes in the app, never inside your bot.
`image`	On price replies — a chart PNG URL.

Stability

There’s no versioning scheme. The request shape is stable, and the response is a discriminated union keyed by type that grows over time as new capabilities ship. Branch on type and handle unknown values gracefully; relaying text verbatim is always safe regardless of what type says.

Three ways to integrate

Your own bot or app

Call the endpoint above directly.

Agent Skill

Drop a SKILL.md into Claude, Cursor, or any Agent Skills–compatible agent.

MCP server

npx -y protos-mcp — works in Claude Desktop, Cursor, or any MCP client.

Paying to use Protos’s data

If you’re building an agent rather than a chat client, Protos also exposes 8 of its data reads as directly payable x402 endpoints — see Agent-Payable Routes.

Get Started

What Protos Can Do

Build on Protos

Pricing

The endpoint

Request fields

Response fields

Stability

Three ways to integrate

Your own bot or app

Agent Skill

MCP server

Paying to use Protos’s data

​The endpoint

​Request fields

​Response fields

​Stability

​Three ways to integrate

Your own bot or app

Agent Skill

MCP server

​Paying to use Protos’s data

The endpoint

Request fields

Response fields

Stability

Three ways to integrate

Paying to use Protos’s data