Your agent will pay anyone who returns a 402. We gave ours the Lazarus Group's wallet as payTo on a healthy seller. Answer: deny, before it signs.
Free, one line on any x402 client: https://t.co/NjftYJCBr6
Built solo in NL. This month: a payee check for agents, a tool check for MCP servers, a monthly x402 activity index.
If you build agents that pay, what check are you still missing? -Sam
We probe the x402 facilitators every hour: does /verify answer, how fast, on which networks.
If your agent's payments fail at random, check the board before you debug your own code: https://t.co/XWQFx2LHnb
A spend cap tells your agent how much it may pay. Nothing in a 402 tells it to whom.
That second check is the one that matters the day a payTo gets swapped.
Before your agent connects to an MCP server, read its tools like a contract: hidden instructions, tools that can pay or delete, who runs it.
We hash the tool list, so a server that quietly changes its tools later gets caught. https://t.co/7VYc5l0TXl
Base x402, last 30 days: the median seller gets about 9 calls per payer. Six sellers get over 100.
Same protocol, very different businesses. Monthly index, free CSV: https://t.co/HTEQGXyXdr
@aa_y_ush@soupsranjan@ChadLedford A one-time enrollment does not stick to later charges. The payee on the next payment can be a different address. Do you check that address each time, or only the agent you enrolled?
Sanctions lists are written in Latin letters. Your supplier's contract says 华为技术有限公司. The China supplier check now screens Chinese names too, as the English name and the pinyin, and tells you which forms it checked.
@PayAINetwork@conclavedao PayAI /verify averaged 224 ms across 168 hourly probes this week, and /supported answered every one. A fast settle still is not a payee check. The 402 for /round names an address, and the agent has to know it is Conclave's. Do you publish that payTo next to the endpoint?
@agentwormhole We check the step before it: is the payTo one this seller actually lists, and is it on OFAC. 1,027 sellers probed nightly. Which of the 3 did your guard miss?
@FlowExecutor@aspernAI Priced volume over a raw event count, yes. Then split it by payer. A big day can be six wallets calling a lot, or a hundred calling a little. Both numbers, or the event count picks a winner it did not earn.
@ChaosTheorX Publisher, scope, last update. Remote payee check, no shell. One Cursor line:
cursor://anysphere.cursor-deeplink/mcp/install?name=factline-kyc&config=eyJ1cmwiOiJodHRwczovL2ZhY3RsaW5lLmRldi9tY3Ava3ljIn0=
Factline, 7 days to 1 Nov: 46 paid calls. 12 starter keys since 30 Oct.
@OpenClawProd Check the body before you settle. Also check the payTo wallet before the call:
npx skills add factline-dev/factline-skills
Factline, 7 days to 1 Nov: 46 paid calls. 12 starter keys since 30 Oct.
No review yet means the payTo is unchecked. OFAC on that wallet is a separate call, before the first payment:
npx skills add factline-dev/factline-skills
Factline, 7 days to 1 Nov: 46 paid calls. 12 starter keys since 30 Oct.
Want that in the same step when the review set is empty?
Since 1 July, EU parcels up to EUR 150 pay EUR 3 customs duty per distinct tariff code, plus import VAT. Our new Apify actor prices a 1688 or Taobao listing landed in the EU, per item.
@apify Try it: https://t.co/W5bhJBc71I
Scraped a few hundred suppliers from 1688 or Alibaba? This one reads your scraper's dataset and checks each unique supplier for $0.01: https://t.co/gRYA0oAZTw
Check a Chinese supplier before you pay it. Now on @apify Store: send the name and the 18-character code from the business licence, get one row back with UFLPA, US Entity List and EU, UN, UK and US sanctions. $0.03 a supplier.
Real run below: one block_review, one pass.