x402factory.ai
https://x402factory.ai/base/sendBase send endpoint. This specific request will send 950000 token atomics to 0x430F4BA3ffDa98ea1814A2fDb3368e6c26f2fc54 on base for token 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913. For Base USDC with 6 decimals, 0.001 USDC = 1000 atomics and 1000 atomics is the practical minimum.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
98.0% avgResponse time
p50 223ms · p95 279msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/7/2026, 12:00:00 AM | 100% | 15 | 196ms |
| 9/8/2026, 12:00:00 AM | 100% | 21 | 224ms |
| 9/9/2026, 12:00:00 AM | 100% | 20 | 224ms |
| 9/10/2026, 12:00:00 AM | 100% | 14 | 212ms |
| 9/11/2026, 12:00:00 AM | 100% | 10 | 206ms |
| 9/12/2026, 12:00:00 AM | 100% | 9 | 188ms |
| 9/13/2026, 12:00:00 AM | 100% | 16 | 245ms |
| 9/14/2026, 12:00:00 AM | 100% | 15 | 232ms |
| 9/15/2026, 12:00:00 AM | 100% | 16 | 220ms |
| 9/16/2026, 12:00:00 AM | 100% | 16 | 236ms |
| 9/17/2026, 12:00:00 AM | 100% | 15 | 238ms |
| 9/18/2026, 12:00:00 AM | 100% | 13 | 227ms |
| 9/19/2026, 12:00:00 AM | 100% | 13 | 195ms |
| 9/20/2026, 12:00:00 AM | 100% | 12 | 210ms |
| 9/21/2026, 12:00:00 AM | 100% | 12 | 202ms |
| 9/22/2026, 12:00:00 AM | 100% | 13 | 208ms |
| 9/23/2026, 12:00:00 AM | 100% | 13 | 251ms |
| 9/24/2026, 12:00:00 AM | 100% | 13 | 213ms |
| 9/25/2026, 12:00:00 AM | 100% | 14 | 224ms |
| 9/26/2026, 12:00:00 AM | 100% | 14 | 226ms |
| 9/27/2026, 12:00:00 AM | 100% | 13 | 211ms |
| 9/28/2026, 12:00:00 AM | 100% | 13 | 237ms |
| 9/29/2026, 12:00:00 AM | 100% | 12 | 254ms |
| 9/30/2026, 12:00:00 AM | 100% | 12 | 231ms |
| 10/1/2026, 12:00:00 AM | 100% | 12 | 224ms |
| 10/2/2026, 12:00:00 AM | 100% | 12 | 216ms |
| 10/3/2026, 12:00:00 AM | 100% | 13 | 203ms |
| 10/4/2026, 12:00:00 AM | 50% | 10 | 185ms |
| 10/5/2026, 12:00:00 AM | 90% | 10 | 222ms |
| 10/6/2026, 12:00:00 AM | 100% | 4 | 212ms |
- Availability
- 98
- Latency
- 100
- Security
- 93
- Transparency
- 61
- Activity
- 5
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base
- Facilitator
- self-hosted
- SDK
- x402-express
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- NameCheap, Inc.
- Domain registered
- 2025-12-04
- Hosting network
- GOOGL-2
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Payments per day
last payment 9/27/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 9/27/2026 | 1 | 0.95 | 1 |
Payout address changed 1 time, last on 9/27/2026
- 0x1234…7890 → 0x430F…fc54 (base) · 9/27/2026
A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.
Only payments settled on chains and facilitators we index.
Response schema
{
"input": {
"bodyFields": {
"amountAtomic": {
"description": "Amount in token smallest units (atomics), as a positive integer string. For Base USDC with 6 decimals, 0.001 USDC = 1000 atomics. You may also provide this field as 'amount' for compatibility.",
"required": true,
"type": "string"
},
"receiver": {
"description": "Base/EVM 0x wallet address that should receive the tokens.",
"required": true,
"type": "string"
},
"token": {
"description": "Optional ERC-20 token contract address (0x...). When omitted, the endpoint uses BASE_USDC for the current BASE_NETWORK.",
"required": false,
"type": "string"
}
},
"bodyType": "json",
"method": "POST",
"type": "http"
},
"output": {
"action": {
"description": "Action performed. For successful calls this is 'build_send_schema'.",
"type": "string"
},
"amountAtomic": {
"description": "Amount in token smallest units (atomics) as provided by the caller. For Base USDC with 6 decimals, 0.001 USDC is 1000 atomics.",
"type": "string"
},
"network": {
"description": "Base network for which the schema was built (BASE_NETWORK env, e.g. 'base' or 'base-sepolia').",
"type": "string"
},
"ok": {
"description": "True on success.",
"type": "boolean"
},
"payer_wallet": {
"description": "Wallet address that paid the x402 fee for using this endpoint (extracted from the settled payment).",
"type": "string"
},
"paymentSchema": {
"description": "x402-compatible exact payment schema that agents and wallets can use to construct a token payment to the receiver.",
"type": "object"
},
"payment_txid": {
"description": "Blockchain transaction id / transaction hash for the x402 payment that unlocked this endpoint, when provided by the facilitator.",
"type": "string"
},
"receiver": {
"description": "Receiver wallet address that should receive the funds (0x...).",
"type": "string"
},
"token": {
"description": "ERC-20 token contract used for the payment schema (either the provided token or the default BASE_USDC).",
"type": "string"
}
}
}