Hi — I run 402.com.tr, a pay-per-call API catalogue for agents, live on Base
mainnet since June 2026. I saw you onboard third-party tool APIs weekly and I
think we fit the gap rather than compete with it.
What we'd bring: 137 tools behind one integration. Onchain risk and safety
(token risk, honeypot/sellability, holder concentration, LP locks, approvals,
sanctions screening), wallet forensics, account-abstraction and paymaster reads,
plus a business-ops family that is not crypto-specific at all — IBAN validation,
EU VAT checksums, E.164 phone normalisation, FX at ECB reference rates,
business-day arithmetic across ~110 countries.
The part you probably can't source elsewhere: B20. We serve the only
tooling I know of for Base's native token standard — seize/burnBlocked
history, Policy Registry freeze checks, rebase multiplier, supply caps, access
model, config lint. If a Base-native agent needs to know whether a B20 token can
be frozen out from under it, right now that answer exists in our catalogue and
approximately nowhere else.
Integration is one endpoint, either way. We expose a hosted Streamable-HTTP
MCP server at https://402.com.tr/mcp — no install, no key, 137 tools from a
single tools/list. Or hit the x402 gateway directly at
https://402.com.tr/api/x402/<service>; both paths run the same handlers and
settle the same way.
Verify anything before you talk to me. No account needed:
curl "https://402.com.tr/api/x402/gas-oracle?free=1" # real answer, free
curl https://402.com.tr/api/catalog # the full 141
curl -X POST https://402.com.tr/mcp -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Settlements are USDC EIP-3009 on Base to
0x973a31858f4d2125f48c880542da11a2796f12d6, so the payment history is on
Basescan, and the live catalogue with its 30-day call and payer counts is
queryable without our cooperation at
api.cdp.coinbase.com/platform/v2/x402/discovery/search?payTo=0x973a....
Where we actually are, so you're not surprised later. Demand is small — on
the order of twenty external paid calls a month. That is the problem I'm trying
to solve and the reason I'm writing: the catalogue and the reliability work are
done, the distribution is not. I'd rather tell you that up front than have you
find it in the index.
What I'd want from you is the supplier path — whatever onboarding, pricing split
and SLA expectations look like on your side. Happy to adapt response shapes,
add endpoints you're missing, or run a paid pilot on a subset.
— Şükrü, 402.com.tr · sukrutkrdg@gmail.com
Hi — I run 402.com.tr, a pay-per-call API catalogue for agents, live on Base
mainnet since June 2026. I saw you onboard third-party tool APIs weekly and I
think we fit the gap rather than compete with it.
What we'd bring: 137 tools behind one integration. Onchain risk and safety
(token risk, honeypot/sellability, holder concentration, LP locks, approvals,
sanctions screening), wallet forensics, account-abstraction and paymaster reads,
plus a business-ops family that is not crypto-specific at all — IBAN validation,
EU VAT checksums, E.164 phone normalisation, FX at ECB reference rates,
business-day arithmetic across ~110 countries.
The part you probably can't source elsewhere: B20. We serve the only
tooling I know of for Base's native token standard — seize/
burnBlockedhistory, Policy Registry freeze checks, rebase multiplier, supply caps, access
model, config lint. If a Base-native agent needs to know whether a B20 token can
be frozen out from under it, right now that answer exists in our catalogue and
approximately nowhere else.
Integration is one endpoint, either way. We expose a hosted Streamable-HTTP
MCP server at
https://402.com.tr/mcp— no install, no key, 137 tools from asingle
tools/list. Or hit the x402 gateway directly athttps://402.com.tr/api/x402/<service>; both paths run the same handlers andsettle the same way.
Verify anything before you talk to me. No account needed:
Settlements are USDC EIP-3009 on Base to
0x973a31858f4d2125f48c880542da11a2796f12d6, so the payment history is onBasescan, and the live catalogue with its 30-day call and payer counts is
queryable without our cooperation at
api.cdp.coinbase.com/platform/v2/x402/discovery/search?payTo=0x973a....Where we actually are, so you're not surprised later. Demand is small — on
the order of twenty external paid calls a month. That is the problem I'm trying
to solve and the reason I'm writing: the catalogue and the reliability work are
done, the distribution is not. I'd rather tell you that up front than have you
find it in the index.
What I'd want from you is the supplier path — whatever onboarding, pricing split
and SLA expectations look like on your side. Happy to adapt response shapes,
add endpoints you're missing, or run a paid pilot on a subset.
— Şükrü, 402.com.tr · sukrutkrdg@gmail.com