doraemon-chat

doraemon-chat

You are helping the user interact with a running doraemon gateway node — a decentralized AI gateway that accepts USDG micropayments on X Layer (eip155:196) and routes requests to 18 frontier models.

What you need from the user

Ask for (or infer from context):

• Gateway URL — the base URL of the doraemon node (e.g. http://localhost:3000). If not provided, default to http://localhost:3000.
• Message — what they want to ask the frontier model.
• Model — which model to use. If not specified, call /doraemon/setup first to show available models and let the user pick.

Flow

Step 1 — Discover available models

curl -s -X POST <gateway>/doraemon/setup \
  -H "Content-Type: application/json" \
  -d '{}'

Show the user the availableModels list (id, provider, estimatedCostPerRequest). Save the returned sessionId.

Step 2 — Select model

curl -s -X POST <gateway>/doraemon/select-model \
  -H "Content-Type: application/json" \
  -d '{"sessionId": "<sessionId>", "model": "<chosen-model>"}'

Optionally include "systemPrompt" if the user wants to customize the assistant's persona.

Step 3 — Send message (first call — will get 402)

curl -s -X POST <gateway>/doraemon/chat \
  -H "Content-Type: application/json" \
  -d '{"sessionId": "<sessionId>", "message": "<user message>"}'

The server responds with HTTP 402 and a paymentRequirements object. Show the user:

• The amount in USDG (e.g. ~0.0480 USDG)
• The network (eip155:196 = X Layer, zero gas)
• Instructions: sign an EIP-712 + EIP-3009 authorization with their wallet, encode as base64 JSON, pass as X-PAYMENT header

Step 4 — Retry with payment header

curl -s -X POST <gateway>/doraemon/chat \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <base64-encoded-signed-payload>" \
  -d '{"sessionId": "<sessionId>", "message": "<user message>"}'

Display the response message to the user. Show usage.estimatedCost and payment.requestId for tracking.

Step 5 — Multi-turn follow-up

Subsequent messages in the same session reuse the sessionId. Conversation history is maintained server-side automatically.

Check settlement status

curl -s <gateway>/doraemon/settlement/<requestId>

Check usage

curl -s <gateway>/doraemon/usage/<sessionId>

Notes

• The gateway self-hosts on any machine — run npm start in the doraemon repo to spin one up.
• Models without a configured API key are hidden from the /setup response automatically.
• Streaming is available at POST /doraemon/chat/stream (SSE).
• To clear conversation history, send "clearHistory": true in the chat body.