Docs / Reference / REST

REST API

Every tool has a GET equivalent under /api/v1. CORS is open, responses are JSON, and the shapes match the MCP tools exactly.

EndpointMCP equivalent
GET /api/v1/search?q=pepe&limit=10search_tokens
GET /api/v1/tokens/{id|symbol|address}?chain=baseget_token
GET /api/v1/tokens/{id|symbol|address}/riskget_risk_signals
GET /api/v1/market?ids=bitcoin,ethereumget_market_data (by id)
GET /api/v1/market?limit=100&page=1get_market_data (top by cap)
GET /api/v1/trending?source=dex&chain=solana&limit=15get_trending
GET /api/v1/new?chain=base&minLiquidityUsd=10000get_new_tokens
GET /api/v1/globalget_global_stats
GET /api/healthLiveness + version
GET /skill.mdAgent-readable instructions (Markdown)
GET /llms.txtIndex of this site for LLM crawlers
example
curl -s "https://coinfactory.ai/api/v1/tokens/pepe/risk" | jq '.level, .signals[0]'

Status codes

400 invalid params (with issues[]), 404 unknown token, 429 you are over the rate limit, 502/503 an upstream provider failed or throttled us (honour retry-after).

Rate limits, cache TTLs and the providers behind each endpoint are on the limits & data page. Response fields match the MCP tools exactly.