Developers

One paste. Your agent does the rest.

Palate gives agents a small set of HTTP routes and an MCP surface. Hand your agent the setup prompt and it configures itself from palate.inc/install — the query spends your unlock or credit balance, no wallet and no quote step. Use @handles or scope to narrow.

Install runbook OpenAPI Rendered SKILL.md
Agent hot path
GET /api/palatesPOST /api/ask/queryPOST /api/ask/quoteGET /api/palates/<slug>/channelsPOST /api/palates/<slug>/queryGET|POST /mcpGET|POST /<slug>/mcp
Quickstart

From API key to answer in one POST.

1. Let an agent set it up

The easiest path: paste the setup prompt from your account settings into your agent. It fetches palate.inc/install and wires up transport, key, scope, and a test query itself.

Set up Palate by following https://palate.inc/install
and use this key when it asks: palate_your_key_here

2. Or copy your API key

Create a Palate API key in settings. Send it on every request as the palate-api-key header. Treat it like a password. Base URL is https://palate.inc.

palate-api-key: palate_your_key_here

3. Ask a question

POST to the same retrieval surface as the homepage ask box. paymentMode is required with an API key — it spends the key owner's unlocks or credits. No wallet, no quote step.

curl -X POST https://palate.inc/api/ask/query \
  -H "palate-api-key: palate_your_key_here" \
  -H "content-type: application/json" \
  -d '{
    "question":"What should I understand from @handle?",
    "paymentMode":"unlocks"
  }'

4. Or get raw chunks

Add mode:"raw" to get the ranked source chunks back instead, so your agent can resynthesize in its own voice for its human.

curl -X POST https://palate.inc/api/ask/query \
  -H "palate-api-key: palate_your_key_here" \
  -H "content-type: application/json" \
  -d '{
    "question":"What should I understand from @handle?",
    "mode":"raw",
    "paymentMode":"unlocks"
  }'

HTTP and MCP at parity

Identical capabilities either way. Global MCP at/mcp reaches global and collection mentions; /<slug>/mcppins one Palate. Send your Palate API key in the palate-api-key header to pay from your balance.

{
  "mcpServers": {
    "palate": { "url": "https://palate.inc/mcp" }
  }
}
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "palate_query",
    "arguments": {
      "question": "What should I understand from this expert?",
      "scope": { "kind": "global" },
      "paymentMode": "unlocks"
    }
  }
}
Advanced

On-chain pay-per-query.

For wallet-native agents without a Palate account. Make the normal query call with no API key — you get a 402 payment challenge (MPP/Tempo or x402). Your payment client pays and retries the same call automatically; gas is sponsored, so you only sign the payment authorization. No separate quote step.

Download OpenAPI

MPP / Tempo

USDC on Tempo via the MPP charge flow. The 402 returns a WWW-Authenticate: Payment challenge; an MPP client pays and retries. Palate sponsors gas, so the content price is all the agent plans around.

x402 over Base

USDC on Base via the x402 flow against the same query endpoint. An x402 client reads the PAYMENT-REQUIRED challenge, settles, and retries. Scope is global, one Palate, or explicit public handles.

Public shapes only. On-chain payment is handled by your agent's x402 or MPP client — it pays the 402 challenge and retries. See /install. To run a paid query yourself, use an API key from settings.

GETreadyRun a call to see the response shape.
Tool responses appear here.