ChatRIPMCP

Remote MCP and REST API

Bring historical legends into your agent.

Connect MCP clients, REST tools, and wallet-capable agents to the same ChatRIP legends. Agents can discover valid slugs, ask grounded questions, and receive citations or structured JSON.

Setup Instructions
MCP endpointhttps://chatrip.app/mcp
Endpointchatrip.app/mcp
REST API/api/v1/legends/chat
x402 USDC/api/v1/legends/chat/x402
TransportRemote Streamable HTTP
AuthOAuth or developer key
MCPNo credit used
What agents can do

Ask the archive from anywhere.

Discover legends

Agents can call list_legends to find valid slugs and avoid guessing names.

Retrieve historical sources

Agents can call get_legend_context with a question to get profile data and cited source passages, then write the answer themselves.

Show citations

When source retrieval is used, responses include citations and excerpts so the agent can show where the answer came from.

Manage access

OAuth clients can connect directly, while bearer-token clients can use developer API keys that expire and can be revoked. MCP uses no credit. Paid REST API usage belongs to the linked ChatRIP account.

Connection flow

Three steps, then your agent can ask a legend.

  1. Point the client at the endpoint.Use https://chatrip.app/mcp as the remote MCP server URL.
  2. Authenticate.Use the OAuth browser flow when supported, or create a developer API key from your ChatRIP account for bearer-token clients. MCP uses no credit. REST API chat usage is tied to the linked account. Wallet-capable REST agents can use the separate x402 endpoint instead of a stored key.
  3. Verify the tools.Confirm the client sees list_legends and get_legend_context, then send a short test prompt.
API key lifecycle

Checking account access.

Developer keys are tied to your ChatRIP account so agent access can expire automatically and be revoked later.

Agent setup

Paste-ready instructions

REST API

Use ChatRIP from any HTTP client

Create a developer key from your ChatRIP account. Wallet-capable agents can use the separate x402 paid endpoint.
Command or config
curl https://chatrip.app/api/v1/legends \
  -H 'authorization: Bearer chrip_sk_...'

curl -X POST https://chatrip.app/api/v1/legends/chat \
  -H 'authorization: Bearer chrip_sk_...' \
  -H 'content-type: application/json' \
  --data '{
    "legendSlug": "marcus-aurelius",
    "prompt": "How should I handle distraction today?"
  }'

curl -X POST https://chatrip.app/api/v1/legends/chat/x402 \
  -H 'content-type: application/json' \
  --data '{
    "legendSlug": "marcus-aurelius",
    "prompt": "How should I handle distraction today?"
  }'
Paste into your agent
Set up ChatRIP REST API access for this agent.

Bearer-key provisioning:
1. Ask me to create a ChatRIP developer API key from https://chatrip.app/mcp-setup.
2. Store the key securely as CHATRIP_API_KEY.
3. Do not write the raw key to source control.
4. REST API chat calls use the linked ChatRIP account. MCP and ChatGPT tools only read profiles and sources.

x402 payment option:
If this agent supports x402, use https://chatrip.app/api/v1/legends/chat/x402 for paid stateless chat requests. Handle HTTP 402 by paying the advertised USDC requirement, then retry with PAYMENT-SIGNATURE. Do not send Authorization bearer keys to the x402 endpoint, and do not send conversationId.

API:
List legends: https://chatrip.app/api/v1/legends
Ask a legend with bearer auth: https://chatrip.app/api/v1/legends/chat
Ask a legend with x402 payment: https://chatrip.app/api/v1/legends/chat/x402
Bearer authentication: Authorization: Bearer $CHATRIP_API_KEY

After setup, list legends and then ask marcus-aurelius a short test question. Return the answer plus citations if present.

Deprovisioning:
When I ask you to remove access, tell me the key prefix in use and ask me to revoke it from the ChatRIP MCP/API setup page.
  • Developer keys are issued from a signed-in ChatRIP account.
  • REST API chat usage is tied to the linked ChatRIP account. MCP tools use no credit.
  • x402 calls are stateless paid requests and do not require a ChatRIP account key.
  • Only the key prefix is shown later, so copy the raw key when it is created.
  • Revoke keys from the setup page when an agent, laptop, or deployment no longer needs access.