SingIt lets AI agents pay for digital services without ever receiving wallet keys. CA: 0xc2c1e0b7C401e6217193732272444D928646eba3
Europe
Joined January 2023
- Tweets1K
- Following25
- Followers977
- Likes1.9K
6.4 million agent payments in 35 days, and the average is under 2 cents.
A BeInCrypto count of x402 traffic on Base and Solana: $119,947 moved in total, 90.8% of payments below one cent.
That is machine commerce today: high frequency, tiny value. Nobody approves a one-cent payment by hand, and nobody hands an agent open money either. Caps are what make the next digit possible.
Your agent needs an LLM. It does not need your API keys.
Our x402 endpoint is open: Claude, GPT, Gemini, Grok, DeepSeek, Qwen and more behind one OpenAI-compatible API, paid per call in USDC on Base or Solana. Nothing is charged without an answer.
Just looking? The free tier gives 20 answers a day. No key, no payment.
Try it free:
curl ask.singitai.app/v1/chat/com… -H "Content-Type: application/json" -d '{"model":"free/deepseek-v4.1-flash","messages":[{"role":"user","content":"hi"}]}'
Models and pricing: ask.singitai.app/v1/models
Discovery: ask.singitai.app/.well-known…
SingIt retweeted
What we shipped this week, the unglamorous edition.
After the hackathon audience award earlier this week, I spent the week on plumbing instead of demos. Four PRs merged. Here is what changed and why it matters.
Every Base transaction we send now carries our ERC-8021 builder code, so Base can attribute the activity. The CDP SDK could not attach the suffix to USDC transfers, so we build those transfers by hand now. Each non-zero suffix byte costs 16 gas.
Wallet balances no longer depend on Alchemy's free tier: any Base RPC works, once we fixed a Cloudflare 403 caused by Python's default user agent. npm audit is green, 46 tests pass.
The hackathon took 30 hours. Making it dependable takes the weeks after. What did you ship this week?
The SDK default was no spending cap at all. That is the bug everything else sits on. Limits belong outside the library: set by the owner, enforced before anything is signed. A cap the agent can talk past is not a cap.
Critical x402 SDK Flaw Could Let Malicious APIs Drain AI Agents’ Token Balances thehackernews.com/2026/10/cr…
Banks flagging agents that act without instructions is exactly what a budget is for.
The agent gets a capped allowance, not the account, and anything past the cap is declined before money moves.
MAJOR US BANKS DETECT AI AGENTS ACCESSING CUSTOMER ACCOUNTS, SOME ACTING WITHOUT USER INSTRUCTIONS
Major US banks are detecting third-party AI agents accessing customer accounts, with some appearing to take actions independently of user instructions, according to Axios.
Banks are struggling to distinguish human activity from AI agents, determine whether agents have user permission, and identify when an agent has gone rogue.
Morgan Stanley, JPMorgan, Bank of America, and Citi are restricting third-party AI agents over concerns they could move funds, make purchases, or execute transactions without authorization.
One banking executive described the situation as “horrifying,” as financial institutions race to contain the risks posed by increasingly autonomous AI systems.
Mastercard's Agent Pay for Machines demo: one budget, nine payments, two merchants, one human approval.
That's the shape agent spending is settling into. You approve the rule once, the agent pays inside it.
SingIt runs the same rule on USDC over x402: a per-purchase cap, a daily cap, and anything past them refused before it's signed.
Separate agent profiles with their own spending cap is the right call.
That's the whole model: the agent gets a budget, not your card, and anything past the cap is refused before it's paid.
AI shopping agents just got a front door at Walmart.
While Amazon blocks agents, Walmart announced an MCP server called Agent Gateway:
→ Approved agents can search Walmart and Sam's Club inventory and buy for you
→ You don't have to share personal info or purchase history with the agent
→ Next month: a separate profile per agent in your account
→ Require approval per purchase, or pre-approve up to a spending limit
The rules: agents can't see payment details, can't act beyond what you asked, and get blocked if they break the terms.
Walmart's returns policy still applies if an agent gets it wrong.
It already works with Meta's Muse, ChatGPT and Gemini.
techcrunch.com/2026/10/21/wh…
SingIt retweeted
Hi everyone, here’s what’s been happening over the last two days at the hackathon: we’ve built an MCP server, but it’s not public yet – we need to check it for bugs and vulnerabilities. We were a bit short on time, with only about 30 hours in total.
And we won the audience award for our project. I’ll have a rest today, and carry on working tomorrow.
SingIt retweeted
I just finished my pitch at the hackathon when i talk about @SingItAgent and what i build, so now I can finally relax.
87% of x402 payments are under 10 cents, per Chainalysis.
Nobody approves a 3-cent payment by hand. Nobody should approve 400 of them either.
So in SingIt you approve the rule once: a per-purchase cap and a daily cap. The agent pays inside them on its own, and anything past them is refused before it's signed.
Some x402 buyers sign only one scheme: exact. Our paid API only offered upto, metered to the token. So those agents got a 402 they couldn't pay.
Now fixed. Chat routes on SingIt's API offer both, on Base and Solana:
upto: you pay the real token cost, never above the ceiling
exact: you pay that ceiling flat, no metering
And an empty probe now gets a real 402 on images, speech and search too, so x402 indexers can list them.
Thanks @vet402_com your probes caught both.
Circle just made the selling side of x402 a Claude Code plugin. Expect a lot more paid endpoints.
The buying side needs the same care. An agent that can pay any of them still needs a per-purchase cap and a daily cap it can't raise. That's the part SingIt does.
Circle, the company behind USDC, released official skills that teach Claude Code to build with stablecoins.
→ Charge AI agents per API call in USDC, using x402
→ Send, approve and verify USDC on EVM chains and Solana
→ Bridge USDC across chains with CCTP
→ One USDC balance across chains, with transfers in under 500 ms through Circle Gateway
→ Build on Arc, Circle's chain where USDC pays for gas
Install:
/plugin marketplace add circlefin/skills
/plugin install circle-skills@circle
It also includes Circle's MCP server, so Claude reads Circle's current docs and SDKs while it builds.
github.com/circlefin/skills
SingIt retweeted
Elon says Grok Bot can pay for itself. The bigger unlock is agents paying for things at all
what that actually needs:
> a budget, not your card
> caps the model can't raise
> price re-checked at the moment of payment
> one signature to cut it off
that's what I'm building with SingIt: USDC over x402 on Base and Solana
My read: Grok Bot plus agent payments is where this gets wild @Bot
Spend alerts don't help at 3am. By the time you read one, the money is gone.
So SingIt doesn't just alert. A watcher reads the chain, not our own records. On base and solana, if money goes anywhere except your agent, or spends come in an unusual burst, it pauses your limiter first and tells you second.
You wake up to a paused budget, not an empty one.