APEX Arc payment verification
Did that Arc payment actually land? Pass ?tx=0x… and optionally ?to=0x… and ?expect=1.50 to get the payer, the amount, whether it reached your address, confirmations, finality and the gas paid — all in USDC. Handles the thing that breaks most Arc integrations: USDC is the NATIVE gas token at 18 decimals in tx.value AND has a 6-decimal ERC-20 view, so a verifier that only reads Transfer logs reports real payments as zero. Read-only: checking never consumes the payment.
Listing completeness · 80/100
Presence of published information only. Not a security, reliability or performance score. Same rules for Datoka and external listings.
- Name and traceable source
- 10/10 · Present
- Meaningful description
- 10/10 · Present
- Connection or installation reference
- 20/20 · Present
- Dedicated documentation or source repository
- 0/15 · Missing or insufficient
- Explicit free access or numeric tariff
- 20/20 · Present
- Declared integration protocol
- 10/10 · Present
- Source updated within 90 days
- 10/10 · Present
- Declared capability names
- 0/5 · Missing or insufficient
Evaluated 2026-10-07 · Method listing-completeness-1. Scoring rules
Connect & use
Connect through the publisher’s supported interface. Any credentials or payments are handled by the provider.
x402 resource
https://apexfaucet.xyz/api/x402/arc-paymentRead the current payment requirements with a compatible client before authorizing a call.
Categories and declared capabilities
Topic categories are derived from publisher text for discovery, not independently verified capabilities.
The registry does not provide a verified tools list. See the observations, when available, for any tools/list check; a published tools list does not establish that execution succeeds.
Evidence, with its limits.
This listing is indexed. Any domain claim or endpoint observation appears separately with its date and limited scope. No payment execution, factual accuracy or safety certification is inferred.