Losbeto — Market Data for AI Agents

Official registry AI and agents

Market data, LLM gateway, ML forecasts, batch+bundle, self-building catalog. USDC via x402 + MPP.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http losbeto-market-data-for-ai-agents 'https://api.losbeto.xyz/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "losbeto-market-data-for-ai-agents": {
            "type": "http",
            "url": "https://api.losbeto.xyz/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Losbeto — LLM gateway + market data for AI agents (x402)
  2. Quick start
  3. Base chain reads — priced for loops ($0.001–0.002)
  4. Agent-native: ERC-8004 reputation and wallet verdicts
  5. Plans — one payment, N calls (no settlement latency)
  6. The Brazil moat: point-in-time official statistics
  7. The Brazilian primitives (zero upstream, sub-millisecond)
  8. Transparency — receipts are public
  9. Verify anything, offline
  10. For agents and indexers
  11. Run it yourself
  12. Contact

Losbeto — LLM gateway + market data for AI agents (x402)

Losbeto on x402-list — monitored uptime

One USDC micropayment per call. No signup, no API keys to manage — the payment is the auth. USDC on Base, Solana, Algorand or Polygon.

Flagship: an OpenAI-compatible LLM gateway for agents. POST /v1/chat/completions and GET /llm at $0.005/call on live backends, with a free tier at /llm/free and model list at /v1/models. Behind it, 120 endpoints ($0.001–99.99): Base chain reads, FX, equities, commodities, macro calendar, crypto — plus Brazil's official statistics in depth, which nobody else on x402 covers.

Identity: registered ERC-8004 agent — agentId 87048 on Base, registration file at /.well-known/erc8004.json, domain-verified via /.well-known/agent-registration.json.

Compliance: Grade A 98/100 on x402lint (PASS 23 · FAIL 0) — and listed on x402scan, x402-list, the official MCP Registry (io.github.rmartins1451/losbeto), PyPI and npm.

Trusted in production: 92/100 with $278.98 settled volume (30d) on x402-list · $349+ verified on-chain volume indexed by Roundhouse · 100% uptime and 1,405 transactions (7d) on APIHub · 99.0% uptime (59d) on glama.ai.

Quick start

# free — LLM taste, 5 calls/day
curl "https://api.losbeto.xyz/llm/free?q=hello"

# free — delayed preview of any paid endpoint
curl "https://api.losbeto.xyz/forex-rate?pair=EURUSD&preview=1"

# free — machine-readable plans catalog
curl "https://api.losbeto.xyz/plans"

# paid — IPCA as it was known on 5 Aug 2026 (not as revised since)
curl "https://api.losbeto.xyz/br-asof?series=ipca_12m_pct&date=2026-08-05"
# -> HTTP 402 with the payment challenge; pay and repeat

With an x402 client (EVM):

import { wrapFetchWithPayment } from "x402-fetch";

const fetchWithPay = wrapFetchWithPayment(fetch, wallet);
const r = await fetchWithPay("https://api.losbeto.xyz/llm?q=market%20outlook");
console.log(await r.json());
Pay from Solana, Algorand or Polygon

The 402 challenge lists every network we accept — read it once, then pay on the chain you prefer:

curl -i "https://api.losbeto.xyz/pyth-price?symbol=SOL"
# HTTP 402 — the v2 PAYMENT-REQUIRED header carries the full network list (CAIP-2):
#   eip155:8453 (Base) · solana · algorand · eip155:137 (Polygon)
# the v1 JSON body shows the two legacy short names:
#   { "network": "base",   "scheme": "exact", "amount": ..., "payTo": "0xd5Ba9711..." }
#   { "network": "solana", "scheme": "exact", "amount": ..., "payTo": "GEhr9HCFTR..." }
  1. Pick the accepts[] entry matching your chain — same price on all of them.
  2. Build the payment exactly as the exact scheme requires. Any x402 client with SVM support handles this for you; on Solana the payload is your partially-signed USDC transfer transaction, which the facilitator broadcasts and settles (it also pays the network fee — you only sign).
  3. Re-send the same request with the signed payload in the X-PAYMENT header. The response arrives on that same request — no polling, no webhook.

Algorand and Polygon follow the identical pattern (USDC, scheme exact) — Algorand is the rail our own indexers use for full-catalog round-trips. Settlements from every chain appear publicly in GET /receipts, and GET /agents.json lists the live payment networks machine-readably.

From npm:

npm i -g losbeto-llm   # CLI + client for the LLM gateway (EVM: set LOSBETO_EVM_KEY — Solana/Algorand/Polygon above)
npm i losbeto-mcp      # MCP server package

As an MCP server (Claude Desktop, Cursor, Claude Code):

{
  "mcpServers": {
    "losbeto": {
      "url": "https://api.losbeto.xyz/mcp",
      "headers": { "Authorization": "Bearer <credit-key>" }
    }
  }
}

Get a credit key with one on-chain payment: POST https://api.losbeto.xyz/buy-credits.

Base chain reads — priced for loops ($0.001–0.002)

Raw chain data with an intelligence layer on top. Zero upstream cost (public RPC with short-cache and failover), so these are built to be hammered by agent loops:

EndpointPriceWhat you get
/chain-block$0.001Latest Base block: number, age, gas-used %, base fee
/gas-price$0.001Gas now + ML forecast ~10 min ahead (self-fed Holt double exponential smoothing — every paid call trains the model). Answers send_now or wait_~10min_cheaper with confidence
/chain-balance?address=$0.002ETH + ERC-20 balances (USDC/WETH/cbBTC default, up to 20 via tokens=), nonce, and a wallet-class heuristic (whale / degen / diversified / retail / newcomer)
/chain-ens?name= or ?address=$0.002ENS forward and reverse resolution (Ethereum mainnet) — embedded keccak/namehash, zero dependencies
/chain-tx?hash=$0.002Status, confirmations, value, fee, logs, explorer link. Add &explain=1 for an LLM plain-English explanation of the transaction

Agent-native: ERC-8004 reputation and wallet verdicts

EndpointPriceWhat you get
/agent-reputation?agentId=&clients=$0.010On-chain ERC-8004 identity (owner, tokenURI) plus aggregated feedback from the Reputation Registry (getSummary), for any registered agent. First x402 endpoint serving the ERC-8004 standard
/wallet-verdict?address=$0.020A graded verdict on any Base wallet (WHALE / STEADY / DEGEN / NEWCOMER / GHOST) with an LLM-written roast, idempotent via requestKey, plus a free shareable SVG card at /wallet-verdict/card.svg?address= — built to be posted

Plans — one payment, N calls (no settlement latency)

PlanPayYou get
/buy-credits$0.99$1.25 balance (+25%), 30 days
/buy-credits-5$4.99$6.00 balance (+20%), 60 days
/buy-credits-25$24.99$33.00 balance (+32%), 90 days
/day-pass$2.99unlimited, 24h
/week-pass$9.99unlimited, 7 days
/subscribe-pro$9.99/mo$15 balance monthly (+50%)
/subscribe-whale$19.99/mounlimited, 30 days
/founding-agent$49.99$75 balance (+50%), 180 days, founding badge
/enterprise$99.99/yrunlimited, 12 months

Machine-readable at /plans, human-readable at /pricing. First purchase earns a bonus call, credited to your session token (7 days). The node never discounts list price — it adds value after payment instead.

The Brazil moat: point-in-time official statistics

The problem: the IPCA number you fetch from the Banco Central API today is not the number that was published back then. Official Brazilian series are revised. Any backtest built on the current series silently contains look-ahead bias.

The US has ALFRED for this. Brazil has nothing public.

This node has been recording Brazilian official statistics as they were published, timestamping every reading and signing each day with Ed25519 — continuously, since deploy. That archive cannot be scraped retroactively by anyone, including us.

EndpointPriceWhat you get
/br-pit-prooffreeMerkle roots, signer key, coverage window, verification recipe
/br-asof?series=&date=$0.09The value as known on that date — vintage, not revised
/br-revisions?series=$0.19First print → every correction, with size and observation timestamp
/br-archive?day=$0.09Signed daily snapshot: BCB macro + Ibovespa close
/br-brief$0.50Daily Brazil macro + equity brief, in English

Series tracked: selic_meta_pct, cdi_daily_pct, ipca_12m_pct, igpm_month_pct, usd_brl_ptax, eur_brl.

The Brazilian primitives (zero upstream, sub-millisecond)

Pure computation over Brazilian specifications — no external API in the request path, no rate limit, no provider outage, priced for loops:

EndpointPriceWhat you get
/br-pix-parse?code=$0.010Decode and CRC16-verify a PIX BR Code (EMV-MPM)
/br-pix-code?key=&name=&city=$0.010Generate a valid static PIX BR Code, self-checked by re-parsing
/br-bizdays?from=&to=$0.010Bank business days on the ANBIMA 252 convention
/br-doc?doc=$0.010CNPJ/CPF modulo-11 check-digit validation

Verifiable from outside: GET /zero-upstream.json declares which routes never touch the network.

Transparency — receipts are public

  • GET /receipts — every settlement, public
  • GET /.well-known/honest-revenue.json — signed; separates organic (wallets the operator doesn't control) from operator-test and self-sweep
  • GET /scorecard.json — 24h availability, p50/p95 latency, traffic mix, signed
  • GET /.well-known/erc8004.json — ERC-8004 registration file; live on-chain as agentId 87048

Verify anything, offline

Every observation is a Merkle leaf:

leaf = sha256("<series>|<ref_date>|<value>|<seq>|<observed_ts>")
Ed25519( "losbeto-pit|<day>|<root>" )   # pubkey at /br-pit-proof

Daily roots are optionally anchored on Algorand as zero-value note transactions, so the timestamp does not depend on trusting us.

For agents and indexers

Start at GET /agents.json — outcome-based flows with exact parameters, payment networks, free tier, and pointers to the OpenAPI contract, the x402 manifest, the scorecard and the fidelity recipes. CORS open, cached 1h. ScoutScore, x402scan, x402-list and other rankers: /agents.json, /scorecard.json, /.well-known/fidelity.json, /zero-upstream.json, /bazaar-status. Free probes never charge; a paid route that hits an internal error degrades to a 402 rather than a 500.

Run it yourself

pip install -r requirements.txt
export SOLANA_WALLET_ADDRESS=...      # where payments land
export BASE_PAYTO_EVM=0x...           # optional
export ALGORAND_WALLET_ADDRESS=...    # optional
export BUYER_WALLETS=...              # your own test-buyer wallets, comma separated
gunicorn --workers 2 --threads 8 --preload --bind 0.0.0.0:$PORT nexus_omega:app

Useful env vars: AI_WARMER=1, LLM_DAILY_GLOBAL_CAP, LLM_DAILY_KEY_CAP, PIT_INTERVAL_S, ALGO_ANCHOR_MNEMONIC, X402LIST_TOKEN, EVM_RPC_URLS, ETH_RPC_URLS, PRICE_CHAIN_BLOCK … PRICE_WALLET_VERDICT (per-endpoint price overrides).

Contact

Roberto Martins — roberto.martins622@gmail.com

Missing a series or a market you need? Open an issue. New endpoints get built on request.

MIT licensed.

Frequently asked questions

What is Losbeto — Market Data for AI Agents?

Market data, LLM gateway, ML forecasts, batch+bundle, self-building catalog. USDC via x402 + MPP.

How do I install Losbeto — Market Data for AI Agents?

It runs as a remote server. In Claude Code: claude mcp add --transport http losbeto-market-data-for-ai-agents 'https://api.losbeto.xyz/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Losbeto — Market Data for AI Agents need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Losbeto — Market Data for AI Agents open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Losbeto — Market Data for AI Agents?

It is published by rmartins1451. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.