Agent-Callable Fexr Skills for Any LLM
One skill wires any LLM to Fexr's whole stack through a typed contract — so the calls it makes are the real ones: right endpoints, right params, right auth. No hallucinated APIs.
Pointing an LLM at raw infra breaks in predictable ways.
Ask a model to build against an API it half-remembers and you get confident, wrong code. Three failure modes eat most of the debugging.
The model invents a plausible route like /api/wallet/create that never existed. You find out at runtime, with a 404.
Right endpoint, wrong body — a misnamed field, a string where an amount goes, a missing header. A 400 you have to reverse-engineer.
DPoP, API keys, x402 payment headers — the model guesses the scheme and stalls on 401s instead of shipping.
The skill removes the guessing. It gives the model Fexr's typed contract — every endpoint, parameter, and auth rule, generated from the live registry — so it calls the real thing correctly instead of improvising.
What the skill hands your model.
One typed contract, generated from Fexr's live registry. Add it once; your LLM builds against the real API surface — not its best guess.
28 typed tools generated from Fexr's running services at api.fexr.io/v1/mcp. Names, routes, and types stay in sync with production — the model can't call something that isn't there.
Every tool carries its request and response schema, and where a call is metered, its USDC price. The model validates params before it calls, and budgets a paid call before it makes one.
DPoP, API keys, and x402 payment headers are part of the contract — configured once on the MCP server, or carried in the x402 flow — so the model wires auth correctly instead of guessing the scheme.
Build anything on Fexr.
The skill covers the whole stack — all three families reachable from the same typed contract. Market data is one of them, not the main event.
Prices, fundamentals, flows, and research as typed reads — from asset metrics to smart-money flow and deep research. Every response is schema-typed and carries a freshness age, so the model knows exactly what it got.
Describe a governance model in plain language; the skill orchestrates wallets, liquidity contracts, proposals, member roles, and on-chain execution into a working app — against Fexr's production APIs, typed end to end.
Self-custody wallets, staking and liquidity contracts, and an on-chain execution engine — exposed directly as typed REST with replay-safe webhooks, the same primitives the builder skill calls.
Same task, with and without the skill.
A wallet-balance call, generated two ways. Without the typed contract the model improvises the route and the auth; with it, the call is correct and the auth is already wired.
Works in the LLM you already use.
Add the skill and the same typed catalog is reachable from every major client. Tool-calling, webhooks, and DPoP-gated enterprise endpoints vary by surface.
Everything the skill can reach.
The full typed surface behind the contract — each product callable as an MCP tool, over REST, or paid per call over x402. Reference, not required reading.
Orchestrates wallets, liquidity, proposals, roles and execution from one prompt. Not metered per-call — it composes the APIs below.
Self-custody wallets, staking/liquidity contracts, and the on-chain execution engine, with replay-safe webhooks.
Add the skill in minutes.
api.fexr.io/v1/mcp — 28 typed tools, schemas and prices embedded.402 with the USDC price, pay on Base, and retry with X-PAYMENT.Ship on Fexr without the errors. Add the skill to the LLM you already use, and your model builds against Fexr's real, typed surface — right endpoints, right params, auth handled — from the first call.
Add the MCP server in a minute — no account needed to try it.