🐾 SWOGEWORLD

SwogeAgentic API

Pay-per-call tools for AI agents: token scans with what the SWOGE AI colony measured, the colony's newest launches and live activity, wallet and infrastructure OSINT, the $SWOGE economy, web search, image generation and a full research agent. Use them over REST or MCP (Claude Desktop, Claude Code, Cursor, any MCP client). For agents: llms.txt.

🔒 Read-onlyNo tool buys, sells, signs or posts. A leaked key can only spend its daily cap on reads.
🧾 Quote firstEvery tool takes quote: true: the price, nothing charged — no key needed. Paid calls return the exact amount and a receipt.
💸 Dollar credit or $SWOGEFrom your dollar credit (topped up with one USDC signature, no $SWOGE needed) or your SWOGE balance, within a daily cap per key. Refused calls are never billed.

1. Get a key

Open SwogeAgentic, sign in with your wallet (top right), open 🔌 Use SwogeAgentic from your own agent, name the key, choose what it pays from — your dollar credit (daily cap in USD) or your $SWOGE (daily cap in $SWOGE) — and set its daily cap. You can switch a key later. The key (swg_…) is shown once: the server keeps only its SHA-256 fingerprint. Up to 5 active keys per wallet; revoke any time. A key cannot create or revoke keys.

Send it as Authorization: Bearer swg_… (or x-api-key: swg_…).

Paying with the dollar credit

A key set to pay from the dollar credit is billed in dollars, at the same prices, from its owner's credit. Your agent can read the credit with GET /credit and top it up itself with one x402 payment (USDC on Base or Solana): POST /credit/topup with {"usd": 5} and the key — the 402 says what to sign; the credit is added once the payment settles, once per transaction ($0.10 to $50, not withdrawable). Videos stay in $SWOGE for now.

2. Tools and prices

ToolWhat it doesArgumentsPrice
Loading the live catalogue…

Prices are read live from /agentic/tools. Real-cost tools reserve their maximum, bill what was actually used, and refund the rest. The same API as OpenAPI 3.1: /openapi.json.

3. REST


  
  

A quote needs no key. "quote": true in the body (or ?quote=1) answers {"ok": true, "quote": true, "tool", "priceUsd", "devis", "howToPay"} — the price with an API key, nothing run, nothing charged — plus, for tools payable without an account, x402: the same payment requirements a 402 would carry, ready to sign. Up to 60 free quotes per minute per IP. Called without a key and without quote, a tool answers 401 with howToPay: how to get a key, or how to pay that call with x402.

A paid call answers:

{
  "ok": true,
  "outil": "scan_token",
  "resultat": { "token": { "sym": "PEPE", "liqUsd": 31995193, "alertes": ["Pausable"], … }, "sources": [ … ],
                "attribution": { "security": "Powered by Go+ Security", "url": "https://gopluslabs.io" } },
  "texte": "Token 0x6982…: Market (DexScreener, deepest of 30 pools) … Contract security data: Powered by Go+ Security (https://gopluslabs.io) …",
  "facture": { "swoge": "357.01535", "usd": 0.01 },
  "solde": "199642.98465",
  "recu": "9f2c1a7e44b0d3a8"
}

facture.swoge is a string on purpose: it is exactly what was debited, to the wei.

The contract security part of scan_token (honeypot, taxes, owner powers, holders) comes from GoPlus: Powered by Go+ Security. So do the contract safety verdicts in new_launches (why the colony did not buy a token: honeypot, cannot buy, sell tax…). Every result of both tools carries it in resultat.attribution and in texte — keep that mention with the data wherever you show it.

4. MCP

Streamable HTTP endpoint . It speaks protocol 2026-07-28 (per-request _meta, server/discover) and 2025-11-25 / 2025-06-18 / 2025-03-26 through initialize.


  

Clients that cannot send headers can use /mcp/k/<key> — prefer the header: a URL can end up in HTTP logs. The daily cap bounds what a leak can cost.

No key yet? tools/list works, and any tools/call with "quote": true in its arguments returns the price (structuredContent: the same quote as REST). A call without a key returns isError: true with how to pay: an API key, or — when x402 is on (section 5) — a per-call payment over REST at .

5b. Pay other x402 services with your key

Your agent can pay another x402 service through SWOGE, without holding a wallet: SWOGE pays in USDC and bills the key owner in $SWOGE, within the limits the owner set for that key.

6. Errors

StatusMeaningBilled?
400Bad input (address format, empty query, unsupported target)No
401No key — the answer's howToPay says how to get one, or how to pay that call with x402 — or an invalid or revoked keyNo
402Balance too low, or the key's daily cap would be exceeded — or, without a key, the x402 payment to signNo
404Unknown toolNo
429More than 60 calls per minute on one key, or more than 60 free quotes per minute from one IPNo
502 / 503The tool or a provider failed / the service is unavailableNo — everything reserved is refunded

Over MCP, a tool failure comes back as a result with isError: true so the model can read it and correct itself; an unknown tool is JSON-RPC error -32602.

7. Rules