REST API

The MIKO REST API exposes MIKO's capabilities over standard HTTP. Every request is authenticated with a wallet-signed JWT, and every response is JSON.

Base URL

https://api.mikoprotocol.com

Authentication

Every endpoint requires a Bearer token in the Authorization header. The token is obtained by signing a server-issued nonce with the holder's Solana wallet.

To obtain a JWT through the browser without writing signing code, visit https://api.mikoprotocol.com/dashboard, connect a wallet, sign in, and copy the bearer token. The steps below describe the same flow at the wire level.

Step 1: Request a nonce

curl -X POST https://api.mikoprotocol.com/auth/nonce \
  -H "Content-Type: application/json" \
  -d '{"wallet": "<solana_address>"}'

Response:

{
  "nonce": "5xKQp7vN3aB8cD2eF9gH...",
  "expires_at": "2026-05-27T12:35:00Z"
}

Step 2: Sign the nonce

Sign the nonce string with the wallet's secret key.

// JavaScript / TypeScript
import { Keypair } from "@solana/web3.js";
import bs58 from "bs58";
import nacl from "tweetnacl";

const message = new TextEncoder().encode(nonce);
const signature = nacl.sign.detached(message, keypair.secretKey);
const signatureB58 = bs58.encode(signature);

# Python
from nacl.signing import SigningKey
import base58

message = nonce.encode("utf-8")
signing_key = SigningKey(secret_key)
signed = signing_key.sign(message)
signature_b58 = base58.b58encode(signed.signature).decode()

Step 3: Verify and receive JWT

curl -X POST https://api.mikoprotocol.com/auth/verify \
  -H "Content-Type: application/json" \
  -d '{
    "wallet": "<solana_address>",
    "signature": "<base58_sig>",
    "nonce": "<nonce_from_step_1>"
  }'

Response:

{
  "jwt": "eyJhbGciOiJIUzI1NiIs...",
  "tier": "Holder",
  "expires_at": "2026-05-28T12:30:00Z",
  "quota": {"daily_limit": 5, "remaining": 5}
}

Include the JWT in every subsequent request:

Authorization: Bearer eyJhbGciOiJIUzI1NiIs...

Tier and Quota

The JWT is scoped to the holder's current tier. Tiers are evaluated at JWT issuance based on $MIKO holdings.

Tier	Holdings	Daily Limit	Per-minute Limit
Holder	≥ $100	5 requests	1 RPM
Pro	≥ $1,000	100 requests	3 RPM
Whale	≥ $2,000	300 requests	10 RPM

Wallets holding less than $100 of $MIKO receive 403 tier_insufficient at /auth/verify and cannot obtain a JWT.

Tier and remaining quota are returned in every response under the X-Tier and X-Quota-Remaining headers.

Endpoint Access by Tier

Endpoint	Minimum Tier
`POST /v1/factcheck`	Pro
`POST /v1/narrative`	Pro
`POST /v1/persona`	Pro
`GET /v1/watchlist`	Pro
`POST /v1/insights`	Holder
`GET /v1/narratives/trending`	Holder

Calls to an endpoint above the caller's tier return 403 tier_insufficient.

Endpoints

POST /v1/factcheck

Verify a claim through MIKO's multi-provider fact-check.

Request:

curl -X POST https://api.mikoprotocol.com/v1/factcheck \
  -H "Authorization: Bearer <jwt>" \
  -H "Content-Type: application/json" \
  -d '{
    "claim": "$BONK is announcing a Visa partnership next week"
  }'

Response:

{
  "is_verified": false,
  "verdict_summary": "No Visa press release matches the claim. No official $BONK channel has announced the partnership. The original post traces to an unverified account with a recent history of similar pump-and-dump claims. Independent sources do not converge on this claim.",
  "reasoning": "No Visa press release matches the claim. No official $BONK channel has announced the partnership. The original post traces to an unverified account with a recent history of similar pump-and-dump claims. Independent sources do not converge on this claim."
}

is_verified is true, false, or null.

Example — block a Pump.fun mint preflight when the narrative claim fails verification:

const { is_verified, verdict_summary, reasoning } = await fetch('/v1/factcheck', {
  method: 'POST',
  headers: { 'Authorization': `Bearer ${jwt}`, 'Content-Type': 'application/json' },
  body: JSON.stringify({ claim: form.narrativeClaim }),
}).then(r => r.json());

if (is_verified === false) {
  return { allowMint: false, modal: { body: verdict_summary, evidence: reasoning } };
}

POST /v1/narrative

Get MIKO's narrative read of a Solana mint address.

Request:

curl -X POST https://api.mikoprotocol.com/v1/narrative \
  -H "Authorization: Bearer <jwt>" \
  -H "Content-Type: application/json" \
  -d '{
    "mint_address": "DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263"
  }'

Response:

{
  "symbol": "BONK",
  "mint_address": "DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263",
  "market_snapshot": {
    "price_usd": 0.000018,
    "market_cap_usd": 1240000000,
    "volume_24h_usd": 85000000
  },
  "narrative_summary": "BONK is in an accumulation phase with steady buy-side pressure but limited breakout participation. Volume is elevated against the prior 24h period, but trade size shifts suggest larger wallets are accumulating quietly rather than retail driving the move.",
  "observations": [
    "Buy pressure dominant on 1h timeframe with rising trade count",
    "24h volume up roughly 40% versus prior 24h period",
    "Average trade size declining while trade count rises, consistent with distributed accumulation",
    "Price holding above the 4h high with shallow pullbacks",
    "Wallet inflow steady, no concentration warnings"
  ],
  "snapshot_at": "2026-05-27T12:00:00Z"
}

Example — render a pre-swap context card in a wallet UI:

const data = await fetch('/v1/narrative', {
  method: 'POST', headers,
  body: JSON.stringify({ mint_address: mint }),
}).then(r => r.json());

return <SwapCard
  price={data.market_snapshot.price_usd}
  marketCap={data.market_snapshot.market_cap_usd}
  summary={data.narrative_summary}
  observations={data.observations}
/>;

POST /v1/insights

Get MIKO's insights on a token or narrative topic.

Request:

curl -X POST https://api.mikoprotocol.com/v1/insights \
  -H "Authorization: Bearer <jwt>" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "BONK"
  }'

query accepts a token symbol ("BONK"), a mint address, or a narrative topic ("Solana DePIN", "AI agent infrastructure").

Response:

{
  "query": "BONK",
  "insights": [
    {
      "text": "BONK community staked 1.2B tokens in the dao validator launch (Q1 2026), with no insider unlocks tied to the staking pool. Verified through the official BONK Foundation announcement and corroborating on-chain transaction data.",
      "first_observed_at": "2026-02-14T08:30:00Z",
      "last_confirmed_at": "2026-04-22T16:00:00Z",
      "related_tokens": ["BONK"],
      "fact_check": "verified"
    },
    {
      "text": "Repeated unverified claims of major exchange listings for BONK have circulated since mid-2025; none of the named exchanges (Coinbase, Kraken) have confirmed any listing through their official channels.",
      "first_observed_at": "2025-08-03T14:20:00Z",
      "last_confirmed_at": "2026-05-20T09:00:00Z",
      "related_tokens": ["BONK"],
      "fact_check": "not_required"
    }
  ],
  "total_insights": 8,
  "insights_updated_at": "2026-05-20T09:00:00Z"
}

fact_check is one of verified or not_required.

Example — feed verified insights into an LLM trading agent as grounding context:

data = requests.post('/v1/insights', headers=h, json={'query': symbol}).json()
verified = [i['text'] for i in data['insights'] if i['fact_check'] == 'verified']
prompt = (
    f"Verified knowledge about {symbol}:\n" + "\n".join(verified)
    + f"\n\nLast confirmed: {data['insights_updated_at']}\n---\n{user_question}"
)

GET /v1/narratives/trending

Top narratives in the requested window, ranked by importance and uniqueness.

curl "https://api.mikoprotocol.com/v1/narratives/trending?window=7d" \
  -H "Authorization: Bearer <jwt>"

Query parameters: window = 1d, 2d, 3d, 4d, 5d, 6d, or 7d (default 1d).

Response:

{
  "window": "7d",
  "evaluated_at": "2026-05-27T12:00:00Z",
  "narratives": [
    {
      "summary": "AI agent frameworks and on-chain agent execution have driven sustained KOL discussion this week, anchored by OpenClaw's continued growth and new on-chain agent deployments on Solana.",
      "key_entities": ["AI agents", "OpenClaw", "on-chain agents"],
      "key_tokens": ["CLAWD", "MOLT"],
      "first_observed_at": "2026-05-20T09:00:00Z",
      "last_confirmed_at": "2026-05-27T08:00:00Z",
      "momentum": "dominant",
      "fact_check": "verified"
    },
    {
      "summary": "DePIN narrative gaining steady KOL coverage with new physical-infrastructure tokens entering trading pairs. Discussion shifting from speculative framing to use-case-driven framing.",
      "key_entities": ["DePIN", "physical infrastructure"],
      "key_tokens": ["HONEY"],
      "first_observed_at": "2026-05-22T14:30:00Z",
      "last_confirmed_at": "2026-05-27T07:00:00Z",
      "momentum": "rising",
      "fact_check": "not_required"
    },
    {
      "summary": "Memecoin discussion cooled mid-week as attention rotated toward infrastructure plays. Existing leaders held volume but new launches saw weaker KOL pickup.",
      "key_entities": ["memecoin rotation"],
      "key_tokens": ["WIF"],
      "first_observed_at": "2026-05-21T11:00:00Z",
      "last_confirmed_at": "2026-05-26T18:00:00Z",
      "momentum": "cooling",
      "fact_check": "not_required"
    }
  ]
}

momentum is one of rising, dominant, or cooling.

fact_check is one of verified or not_required.

Up to 5 narratives are returned. key_tokens lists token symbols only. Empty arrays are valid responses.

Example — daily Discord briefing bot driven by a 9am cron:

data = requests.get('/v1/narratives/trending?window=1d', headers=h).json()
msg = f"🗓️ {data['evaluated_at'][:10]} narratives\n"
for n in data['narratives']:
    arrow = {'rising': '↗', 'dominant': '●', 'cooling': '↘'}[n['momentum']]
    tokens = ' '.join(f"${t}" for t in n['key_tokens'])
    msg += f"\n{arrow} {n['summary']}\n   tokens: {tokens}"
webhook.send(msg)

GET /v1/watchlist

Tokens currently on the watchlist, each with a plain-language summary.

curl https://api.mikoprotocol.com/v1/watchlist \
  -H "Authorization: Bearer <jwt>"

Response:

{
  "evaluated_at": "2026-05-27T12:00:00Z",
  "watching": [
    {
      "symbol": "POPCAT",
      "mint_address": "...",
      "attention_level": "rising",
      "summary": "Building KOL momentum over the last 48h with multiple independent sources flagging accumulation. Narrative anchored on a memecoin recovery wave.",
      "first_appeared_at": "2026-05-25T10:00:00Z"
    },
    {
      "symbol": "WIF",
      "mint_address": "...",
      "attention_level": "high",
      "summary": "Sustained attention across the full week with steady mention volume. Coverage tone is neutral-to-positive; no breakout catalyst surfaced yet.",
      "first_appeared_at": "2026-05-20T08:00:00Z"
    },
    {
      "symbol": "CLAWD",
      "mint_address": "...",
      "attention_level": "high",
      "summary": "Strong recurring mentions tied to AI agent narrative dominance. Multiple KOLs framing as a core position for the current rotation.",
      "first_appeared_at": "2026-05-18T11:30:00Z"
    }
  ]
}

attention_level is one of high, rising, or steady.

Example — track MIKO's pre-curation candidate pool to compare with later weekly picks:

data = requests.get('/v1/watchlist', headers=h).json()
for w in data['watching']:
    db.shadow_track.insert(
        ts=data['evaluated_at'],
        symbol=w['symbol'],
        mint=w['mint_address'],
        attention=w['attention_level'],
        first_seen=w['first_appeared_at'],
    )

POST /v1/persona

Generate a response in Miko's voice. Pass the content to react to or the topic to write about; the persona is built in to the model, so no system prompt is sent.

Request:

curl -X POST https://api.mikoprotocol.com/v1/persona \
  -H "Authorization: Bearer <jwt>" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "write a Miko take on why low fees matter for onchain culture"
  }'

Response:

{
  "text": "..."
}

The model writes from the prompt you supply; see Open Model for what it is and how to run the same model locally or over MCP.

Example — power a community bot reply in Miko's voice:

data = requests.post('/v1/persona', headers=h, json={'prompt': user_message}).json()
bot.reply(data['text'])

Error Responses

All errors return JSON with an error field and HTTP status:

{
  "error": "quota_exceeded",
  "message": "Daily quota of 5 reached for Holder tier",
  "retry_after": "2026-05-28T00:00:00Z"
}

Common errors:

Status	Code	Meaning
401	`unauthorized`	missing or invalid JWT
403	`tier_insufficient`	wallet does not hold the minimum $MIKO required to obtain a JWT, or current tier lacks access to the endpoint
429	`quota_exceeded`	daily or per-minute quota exhausted
429	`rate_limit_burst`	per-second burst cap exceeded
400	`invalid_request`	malformed request body
503	`provider_unavailable`	upstream provider unavailable, retry suggested

Rate Limiting

In addition to the daily and per-minute tier quotas, all endpoints have a per-wallet burst cap of 5 requests per second.

Caching

Identical requests within a 5-minute window return cached responses. Cache hits do not count against the daily quota. Response headers:

X-Cache: HIT or X-Cache: MISS
X-Cache-Age: <seconds since cached>

Base URL​

Authentication​

Step 1: Request a nonce​

Step 2: Sign the nonce​

Step 3: Verify and receive JWT​

Tier and Quota​

Endpoint Access by Tier​

Endpoints​

POST /v1/factcheck​

POST /v1/narrative​

POST /v1/insights​

GET /v1/narratives/trending​

GET /v1/watchlist​

POST /v1/persona​

Error Responses​

Rate Limiting​

Caching​

Base URL

Authentication

Step 1: Request a nonce

Step 2: Sign the nonce

Step 3: Verify and receive JWT

Tier and Quota

Endpoint Access by Tier

Endpoints

POST /v1/factcheck

POST /v1/narrative

POST /v1/insights

GET /v1/narratives/trending

GET /v1/watchlist

POST /v1/persona

Error Responses

Rate Limiting

Caching