Brave Search API now accepts agentic payments via the x402 protocol
https://brave.com/blog/search-api-agentic-payments/I do want it to work, so just curious does anyone have any positive anecdotes? Can this naturally get picked up by crawlers?
- The per-API-call return probably needs to be fairly high with obvious value to justify paying for something. Downloading a .tar.gz of the site, rather than a crawler.
- The world seems to be reforming political blocks, so it'll likely be a cross-bloc transaction where the two sides don't have a fiat transfer system available for use.
- Probably something that is politically sensitive in the customer's bloc.
So my guess would be that the first use case will be some illegal service that could have been implemented with an AWS Lambda, probably hosted somewhere questionable (Russia a candidate). Probably branching out into politically sensitive topics.
> People joking that the only people putting money into x402 are the people testing to see if x402 works.
It'll be that way until suddenly it works for someone, like how bitcoin was a joke up until some tipping point where the financiers started moving in. It'll take a big kick initially to convince people figuring out crypto is worth it just for the sake of making a web trade.
It also means that if this starts getting any traction, then we could expect to start a nice bump in prepaid debit card adoption.
No one is willingly going to tack on a variable cost to their business revenue model. At best, the crawlers/users will simply skip your hosts, or operate in places where gleaning data is still perfectly legal. =3
Would love to hear their thoughts and visions of what the web could be at the time.
$5 for 1000 searches. A lot of basic ChatGPT sessions can easily do 30 web searches , which would already cost $0.15 .
This brings up an interesting concern: providing search obviously isn't free. It has been financed through ads thus far. What happens when the majority of searches are done by agents?
Exa is $4 for 1000 searches.
If you want Google results, SerpApi gives 5000 searches for $75. They are not pay-as-you-go, and more searches give you better pricing. Probably if you're setting this up for your whole company you can get a pretty good deal.
The idea of paying for usage is actually very appealing.
People do this intuitively with payments (negative). They'll buy a timeshare or a boat (expensive, "lump" cost) when it would be much cheaper on net to stay at resorts or rent a boat and pay by usage.
They'll pay for subscriptions (automatic payments) rather than pay per experience. Many people will pay $20/mo for Netflix, watch it twice a month, but would never rent movies for $3 on Amazon.
They'll pay a big premium for "unlimited" data plans when this actually makes little sense for anyone vs. paying by usage.
One could easily imagine that, or that your AI provider, being ChatGPT, Anthropic or Cursor or even neo clouds where you run your own compute on, provide a weekly or monthly aggregated payment not just for computes but for paid traffic. They have the balance sheet (sigh) to front it.
You'd pay $20 for compute and $8.7896813 for traffic or you'd have a "budget" of $10 of traffic included in your $30 bundle.
I think customers would accept that if explain that otherwise their queries wouldn't be as nice and also that the providers of content would get a share.
Granted this is for micropayments and each search will most likely cost pennies but it still means loading up some real money into a digital wallet which an agent will blindly (and most likely very inefficiently) spend at its own discretion.
Time will tell, I guess.
Mind you Visa could have implemented this when everyone first asked back in 1999, but hey here we are. Rather than micro payments instead we let ads do their best to ruin western civilization.
for 99% of people the first thing they need to do is to understand x402, Purl Wallet, Stripe-developed CLI wallet and base-native USDC.
Funny how crypto tries to snake itself back into our ecosystem again and is still as shitty as it was bfore.
I can't vouch for the quality of the project.
Monero has slow confirmation times. It requires a 0-conf to be able to do micropayments. Most wallets also require a full 10 confirmations before you can use your balance.
So the missing piece for me isn't 402 itself, it's a budget envelope around it: a per-task cap, client-side dedup/caching of near-identical queries, and a receipt ledger I can audit after the run. Without that, making payment frictionless mostly makes runaway spend frictionless too. Does Brave's proxy do any dedup or idempotency for repeated identical queries, or is that entirely left to the harness?
Why are all of these comment bots trained to keep coming back to something?[1][2]