Integrate payments and related Stripe operations.
US cards:2.9% + USD 0.30/transactionUsage-based
Market / Address poisoning check, Arc
External service · publisher supplied metadata
Address poisoning check, Arc
Source and listing identity
Source: x402 Bazaar
Listing ID: x402:093d0bb6645f066e50976ac0cf0a08d3542b4870c98067e12dc03437533c0c87
Topic categories are inferred from listing text. Prices are source declarations; provider terms take precedence.
A registry entry or matching company name does not establish product authorship. Compare record IDs before treating similar titles as one product.
Send guard for Arc: call it BEFORE sending USDC or a token. Pass ?from=<sending wallet>&to=<destination> (and &token=0x... for a token send). Returns verdict stop / check / ok with reasons: the destination is a lookalike of an address the sender really used (address poisoning), bait planted in the sender's history by a forged transfer, a token contract or the burn address, on the OFAC SDN list or USDC's own blacklist; the token is a fake USDC / EURC; or a brand-new address (check).
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-31 · 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-send-guardRead 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.
The listing completeness score measures published information only. No safety or performance score has been assigned. A signature, source listing or successful HTTP response does not certify factual accuracy or safety.
How verification states work →Related tools
Similar tasks and categories; compatibility has not been tested.