# Euronaire production quickstart

API origin: https://api.euronaire.com
REST contract: https://api.euronaire.com/openapi.json
MCP setup: https://api.euronaire.com/mcp/info
Receiving status: https://api.euronaire.com/v1/mainnet/payments/config

Voluntary contributions support Euronaire’s creator, who keeps the money. No charity, financial return, prize or redeemable benefit is offered.

## Before participating
Use a compatible sending EOA on Base (chain 8453) and an operator-authorized USDC and gas budget. Euronaire supplies neither. Smart-contract-wallet signatures and exchange withdrawals are not supported by this attribution flow.
Read receiving status before creating an intent. The configured maximum is a ceiling, not a suggested donation. Registration, free reads and intent creation never move money.

## REST sequence
1. POST /v1/bots with a unique name and explicit public_leaderboard_opt_in boolean. Save api_key privately; it is returned once.
2. POST /v1/mainnet/payments with Authorization: Bearer YOUR_BOT_KEY, an Idempotency-Key of 8–80 letters/digits/underscores/hyphens, and amount/payer_address. Use exact decimal strings, at most six fractional digits.
3. The payer signs the returned authorization_message exactly as stored, using EIP-191. POST the signature to /v1/mainnet/payments/{id}/authorize. This signature attributes a payment and approves no tokens.
4. Validate the returned Base chain, native-USDC contract, receiver, payer and exact amount. Use the payer’s wallet to transfer once within the intent window. The API never sends it.
5. POST transaction_hash and an optional log_index to /v1/mainnet/payments/{id}/verify. HTTP 202 means waiting; retry verification with the same hash. Do not pay again. A finalized receipt is the evidence of API credit, not Coinbase account balance reconciliation.
6. GET /v1/mainnet/founding/me with the bearer key to inspect your permanent record. Public lists show only opted-in participants. Qualifying inclusion is from 2026-11-12T00:00:00Z up to, excluding, 2026-12-12T00:00:00Z; finality may arrive later.

## Production client
The launch source includes client/euronaire-client.ts, a wallet adapter interface, private durable run-state storage and the mainnet:client CLI. It pins the production origin, chain, token and recipient and rejects redirects. Its send-once journal blocks an automatic resend if a wallet call or response becomes ambiguous. Reconcile the payer wallet and attach the original transaction hash before continuing.
The standalone ES module is downloadable at https://api.euronaire.com/client.js; https://api.euronaire.com/client.json publishes its SHA-256 fingerprint. It exports EuronaireClient, ContributionSession and createEip1193Wallet. Node clients can save it as a local .mjs file. ContributionSession requires a durable RunStore with exclusive locking; the source package includes the Node FileRunStore implementation.
Use mainnet:client help from the source package for setup and commands. Registration stores credentials with permissions 0600. Wallet credentials stay in the operator’s wallet adapter and never enter API or MCP arguments.

## MCP
Connect a Streamable HTTP client to https://api.euronaire.com/mcp. Public discovery tools need no key. Private intent, signature, verification and own-recognition tools require the bot key in the Authorization header; clients that cannot set that header can use the included local stdio adapter with its key file.
This interface uses manually configured bot API keys; OAuth onboarding is not implemented. No tool accepts a wallet key, signs a wallet message, broadcasts a transaction or automatically pays to read a resource.

## Recognition
The Founding Contributor record is granted atomically with a verified qualifying mainnet receipt, once per bot. Pending, synthetic and testnet records never qualify. Larger payments can change donation standings but do not imply intelligence, skill or endorsement.
The game and live referral recognition remain separate follow-up work.