The same data, over HTTP
Every LurkChain tool is also a REST endpoint. One bearer key, JSON back, and the cost of each call in the response. Use it for bots, dashboards and scripts.
Every endpoint calls the same read-only tools the MCP server does, with the same costs. Responses below are real shapes: request a path from your key and you get the same keys back.
Base URL
All paths below are relative to this. Requests and responses are JSON over HTTPS.
https://api.lurkchain.com/v1
Authentication
Send your key as a bearer token on every request. Create and revoke keys in the app under API keys. Keep them on a server and never ship one in a web page.
Authorization: Bearer $LURKCHAIN_API_KEY
Rate limits and cost
60 requests a minute per key. Each response says what it cost and what you have left.
X-RateLimit-Limit: 60 X-RateLimit-Remaining: 57 X-LurkChain-Cost: 1 X-LurkChain-Balance: 4495
Endpoints
Pick an endpoint to see its parameters, an example request and the response shape.
Costs are in data calls, the same as the MCP tools. Plans are shared across MCP and REST.
Responses
Every success has a data field and a meta field. meta holds the cost, your balance and a request id to quote if you write to support.
Lists come in pages. When there is more, meta.next_cursor is set; pass it back as cursor to get the next page.
Numbers in USD are plain numbers, not strings. Times are ISO 8601 in UTC.
Errors
Errors use normal HTTP status codes and the same error codes as the MCP tools. Failed calls are not charged.
| Status | Code | Meaning |
|---|---|---|
| 400 | invalid_params | A parameter is missing or malformed |
| 401 | unauthorized | Key missing, wrong or revoked |
| 402 | insufficient_credits | Balance lower than the cost |
| 404 | not_found | Token, pool or wallet not indexed |
| 429 | rate_limited | Slow down; see Retry-After |
| 503 | source_unavailable | An upstream source did not answer |
Prefer to ask in plain words?
The MCP server gives your assistant the same tools, with no code to write.