I ran a B2B SaaS business for many years. We struggled, pivoted, gained traction, and ultimately sold for $150M. We used Salesforce for our sales pipeline. It was a pain — big, clunky, rigid, and expensive. We were told to hire a consultant just to set it up. Now I'm running a machine-to-machine oracle business. My entire sales pipeline lives in nginx logs.
The oracle problem is old. In the EVM world, Chainlink and friends emerged because smart contracts are sandboxed — they can't make HTTP calls. The only way to get external data on-chain was to push it there through a consensus mechanism with a token economy. That's not a design choice, it's a constraint of the execution environment. The result is clunky, expensive, governance-heavy infrastructure that made sense given the limitations it was working around.
But that constraint doesn't exist for Bitcoin DLCs, AI agents, or any system that speaks HTTP. A DLC oracle just signs a value with a Schnorr key. An AI agent just makes a fetch call. The Chainlink model is massive overkill — you don't need a token, a committee, or a consensus round to get a signed BTC price.
L402 and x402 change the economics entirely. Before them, the only viable oracle business model was subscription APIs or on-chain token systems. Now you can charge per query, in sats or USDC, with no accounts and no API keys. The payment is the authentication. A client either pays or they don't.
Here's what a B2B sales funnel looks like when your product is an HTTP API gated by micropayments:
A new IP hits /openapi.json and /llms.txt. Nothing else. They're reading the spec. In my logs I see this pattern from AI crawlers (ClaudeBot, OAI-SearchBot), developer tools, and direct human visits. The llms.txt hit is particularly telling — that's a file specifically designed for LLM consumption. Someone is using AI to evaluate your API.
Same IP starts sending HEAD requests to specific endpoints. No payment, no data — just checking availability and latency. I've watched a client send 150+ HEAD requests over two days, exclusively on EUR-denominated pairs and VWAP endpoints. BTC/EUR VWAP is their most-hit endpoint. European fintech, probably. They haven't moved yet.
HEAD requests become GET requests. They start hitting endpoints across all categories — crypto, FX, econ, commodities. Still getting 402s, but now they're testing the payment response format, building the client-side L402 or x402 flow. Watched one IP go from openapi.json + llms.txt discovery on day 1 to full catalogue GET sweeps by day 2.
First sats or USDC hits the revenue database. The log entry that makes it all worth it. Both payment rails have cleared — Lightning L402 and USDC on Base via x402. The pattern is always the same: 402, pay, resend, 200.
The whole pipeline is visible with one command:
sudo grep "$(date +%d/%b/%Y)" /var/log/nginx/access.log \
| grep -v "Blackbox\|UptimeRobot\|127.0.0.1" \
| awk '{print $1}' | sort | uniq -c | sort -rn | head -20
Dig into any IP:
sudo grep "IP_ADDRESS" /var/log/nginx/access.log \ | cut -d'"' -f2,6 | head -20
No CRM. No consultants. No tracking pixels. No cookies. No GDPR consent banners. Just IP addresses, HTTP methods, and payment receipts in a SQLite database.
The pay-per-query model means every conversion is a literal transaction. There's no trial period ambiguity, no "monthly active user" metrics to game, no churn rate to calculate. Either sats hit your Lightning node or they don't. Either USDC lands in your Base wallet or it doesn't.
The unit economics are also completely inverted from traditional SaaS. With Salesforce and a human sales team, your cost of acquisition was enormous relative to the first payment. With micropayments, the first transaction is atomic — no relationship, no negotiation, no invoice. The client just pays.
ClaudeBot — Anthropic's web crawler — has been hitting my endpoints for days. Dozens of GET requests across my full catalogue. All 402s. I'm watching an AI model evaluate my API in real time, systematically probing every endpoint. It hasn't paid yet. But it knows exactly where to come when it does.
In traditional SaaS your sales pipeline is a sequence of human interactions — demo requests, trials, negotiations, contracts. The CRM exists to track those interactions and the humans behind them.
In machine-to-machine commerce, the interactions are automated and the "humans" are agents. There's no email to capture, no name to record, no relationship to manage. There's just a pattern in the logs: discovery → evaluation → integration → payment. Each stage is observable. Each transition is a signal.
Grep is my new Salesforce. The terminal is my dashboard. SQLite is my revenue reporting. It's not glamorous. But it's honest, fast, and costs nothing.
Code is truth. Salesforce is toast in an agentic commerce world.
Mycelia Signal is a sovereign cryptographic oracle — 56 signed endpoints across crypto, FX, economic indicators, and commodities. Payable by AI agents via Lightning (L402) or USDC on Base (x402). Try the live demo or read the docs.