Short answers

Nothing. There is no account, no API key and no paid tier. The API is open to anyone, including from a browser.

No, and you cannot opt out either. Facilitators are detected from the chain — if you broadcast an EIP-3009 authorization on Arc USDC, you are in the index within a second or two.

Show proof that the wallet is yours — a page on your own domain, a post from your project account, or docs listing the address. Send it to @wicketprotocol and the label goes in. Names are only added with public evidence, which is why most wallets stay unlabeled.

No. These are public transactions on a public chain and every block explorer shows the same rows. Wicket adds no information that is not already on Arc — no names, no IPs, no linking of addresses to people.

Arc mainnet only, chain id 5042, and only USDC at the predeploy 0x3600000000000000000000000000000000000000. x402 on Base or Solana is out of scope.

Yes. Point your x402 server at facilitator.wicketworld.xyz — no account, no key, nothing to apply for. The integration page has the endpoints and the one detail that usually breaks it, and the facilitator page shows the wallet balance and the limits so you can judge for yourself whether to depend on it.

Nothing, and that is not an introductory offer — it is arithmetic. Taking 1% of every x402 payment on Arc would have earned about $71 so far against roughly $116 of gas. A facilitator fee is not a business on a chain where gas costs more than the median payment. The treasury pays the gas, and in exchange we get to stand where the payments go through.

/verify starts refusing before that happens, which is the part that matters: a facilitator that says a payment is valid and then cannot settle it has made you hand over goods for nothing. Below the halt threshold we refuse up front, and /healthz returns 503. The wallet balance and the remaining daily gas budget are both public, so you never have to guess how much room is left.

Roughly one block behind the chain. The indexer reads every block continuously; a settle is usually queryable a couple of seconds after it lands.

Check the definitions first, because they usually differ. Wicket counts on-chain EIP-3009 settlements on Arc only, excludes reverted transactions from totals, and excludes plain transfer() calls entirely. Anyone counting HTTP 402 responses, or several chains together, will get a different figure for good reasons. The rule is written out in full under Methodology.

Because nobody has identified them. That is the finding, not a defect — public discussion of x402 on Arc names two operators, and the chain shows many more. See Methodology.

Yes, under CC BY 4.0 — credit wicketworld.xyz with a link. That covers charts, tables and quoted figures. No permission needed.

Not today. Be reasonable and cache what you can. If limits ever become necessary they will be documented on the API page before they are enforced.

Tell @wicketprotocol and include a transaction hash. A concrete counter-example gets fixed fastest.

No. Wicket is an independent project. Arc is built by Circle, and Circle runs one of the facilitators listed here, but there is no relationship beyond reading the public chain.

Yes. $WICKET is live on Arc at 0x06E0Ec452120316fcb0240a20aA461e0a1A7b329, launched on Argus with no presale, no whitelist and no team allocation. Liquidity was locked in the transaction that created the pool. The address is published here and on @wicketprotocol, nowhere else.

Check the address against the one on this page, character by character. There is exactly one $WICKET contract and any other is somebody else's token using our name. Wicket will never DM you first, never run an airdrop claim page, and never ask for a private key or a seed phrase.

A hardened x402 facilitator, built to close attacks published against the protocol, with a test reproducing each one. Progress is shown on the front page and no dates are promised.