Everyone is excited about agentic AI. Agents that book travel, manage portfolios, execute trades, negotiate contracts. The vision is compelling: software that doesn't just advise but acts.
The payment rails are starting to arrive. x402 lets an agent pay for an API call with USDC on Base. L402 lets it settle with Lightning sats. No accounts. No OAuth. No billing portal. A machine makes a request, pays, gets a response. That's genuinely new.
But payment rails are only half the picture. For an agent to act, it needs to know things. Current prices. Real-world data. Verifiable facts it can reason over and stake decisions on. And here's where the infrastructure gap opens up.
The data problem nobody is talking about
Most data APIs were designed for humans. You sign up. You get an API key. You agree to terms of service. You stay within rate limits. You pay a monthly subscription whether you used it or not. None of that works for agents.
An agent doesn't have a billing email. It can't click "confirm your account." It doesn't know ahead of time whether it will need one API call this month or ten thousand. It needs to be able to call a data source, pay atomically for that exact call, get a verified answer, and move on — with no prior relationship with the data provider.
The existing data infrastructure wasn't built for that model. It was built for developers building products for humans.
The oracle problem, restated
In crypto, "the oracle problem" refers to the challenge of getting real-world data onto a blockchain in a trustworthy way. You can't just trust whoever is feeding you the data — you need the data to be signed, sourced, and independently verifiable. That problem generalizes.
An agent acting on a price feed needs to know: is this data real? who signed it? can I verify it without trusting the provider? If an agent is going to execute a trade, trigger a contract, or make a financial decision based on a number, that number needs to come with proof.
Most APIs don't provide that. They give you a JSON response and ask you to trust them.
What we built
I've been building Mycelia Signal — a sovereign price oracle designed from the ground up for the agent-commerce stack.
The idea is simple. An agent makes a request. It pays per query — 10 sats via Lightning (L402) or $0.001 USDC on Base (x402). It gets back a cryptographically signed price attestation in a canonical format it can verify independently against a known public key.
No API keys. No accounts. No subscriptions. Just: call, pay, verify.
bashcurl https://api.myceliasignal.com/oracle/btcusd
→ 402 Payment Required (Lightning invoice or x402 USDC details)
Pay, resend with proof of payment
→ signed attestation: v1|BTCUSD|84231.50|USD|2|2026-03-06T...|nonce|sources|median
Every response is a pipe-delimited canonical string — pair, price, currency, decimals, timestamp, nonce, sources, method — signed with secp256k1 (L402) or Ed25519 (x402). An agent can verify it without calling home. The public key is published. The signature is deterministic.
We currently cover 11 pairs across crypto and FX: BTC/USD, ETH/USD, SOL/USD, EUR/USD, XAU/USD, and EUR-denominated crosses. Each aggregates multiple independent sources — exchanges, central banks, bullion dealers — using median or VWAP methods.
There's also a free preview endpoint for every pair. No payment, unsigned, up to 5 minutes stale — useful for development, prototyping, or any use case where cryptographic attestation isn't required.
The pattern, not just the product
Crypto price data is the obvious starting point. The market is liquid, the sources are available, the use cases for agents are clear. But the pattern generalises to any category where agents need verified, pay-per-query data.
Weather. Shipping rates. Commodity prices. Sports results. Election outcomes. Anything an agent needs to know in order to act.
The infrastructure requirement is the same in every case:
No prior relationship required
Atomic payment per query
Cryptographic proof of data provenance
Machine-readable, deterministic format
Independent verification without trusting the provider
That's the plumbing. It's not glamorous. It won't trend on Twitter. But without it, agents are making decisions on data they can't verify, from providers they can't pay without human intervention, in formats designed for dashboards rather than reasoning engines.
Where this fits
The agent commerce stack is being assembled piece by piece. Coinbase's x402 protocol handles the payment layer. Lightning's L402 handles it on the sats side. Wallets and execution layers are maturing.
Data infrastructure is the missing piece that doesn't have a name yet.
Mycelia Signal is a small, focused answer to that — starting with price data, building toward a broader model where any real-world fact can be requested, paid for atomically, and returned with cryptographic proof of provenance.
Boring. Simple. Exactly what the stack needs.
Try it: https://myceliasignal.com
Docs: https://myceliasignal.com/docs
Free preview (no payment): curl https://api.myceliasignal.com/oracle/btcusd/preview
OpenAPI spec: https://myceliasignal.com/openapi.json
Built with x402, L402, FastAPI, and an unhealthy interest in boring infrastructure.
Top comments (0)