FAQ
The technical questions. Errors, credits, rate limits, suspension, and what happens when something fails.
This page is the technical FAQ, the questions you ask after you integrate. The questions you ask before you spend anything, what a drop costs, which chains, how a run's money splits, live on amnt.io/faq.
No. On the x402 rail, 402 is the protocol working: the server answers with the price, the caller pays in USDC, and resends the same request with the payment header. See Developers to x402.
On the API-key rail a 402 means something different, that your Balance is too low for the run. Top up and retry.
Yes, automatically. Credits come out when the run starts and go straight back if anything throws, without you asking. A failed run is never a paid run. The SVG API validates everything it can before charging at all.
Per key, set when the key is created. A 429 carries a Retry-After header in
seconds. See Developers to Rate limits.
Because it really draws. Generation is not a lookup. The route allows 300 seconds; if your client cannot hold a connection that long, treat a timeout as "still running" and poll the result URL rather than retrying, because a retry is a second paid call. See Long runs.
An agent is suspended automatically when its failure rate goes above 20% over its last 50 runs. This happens without anyone noticing, because a broken agent burns money and produces nothing.
The fix is to find what changed: a provider setting now out of range, a slot accepting values the recipe cannot handle, or the model itself behaving differently. Edit the agent, which creates a new version, test it in the Studio, and republish. The new version starts from a clean record.
Unlock buys unlimited use, never the ability to read it. If buyers could see the recipe after unlocking, nobody would ever unlock a second one from the same creator. The whole product depends on the recipe staying secret regardless of who has paid for what. See Buyers to Unlock & ownership.
Image count is locked by the creator at publish, never chosen by the buyer per run. If it were buyer-controlled, someone could request ten images at a one-image price and every run would cost more to fulfil than it earned. See Concepts to Pricing.
No. Everything is priced in USD, credits, costs and the price floor alike, specifically so a swing in an exchange rate cannot silently erode a creator's margin. See Platform to Money rules.
From what a real run of the agent costs, measured, never guessed. So no run is ever sold for less than it takes to deliver.
An agent edit creates a new version rather than silently changing what is already live. Anyone who unlocked the recipe, or any code integrated against a specific version, keeps the behaviour it was built against. See Creators to Publishing.
A collection run is a snapshot. Generating copies the chosen parts into a new collection row, so renaming a trait later never repaints pieces that are already made.
No. Wallet connection goes through WalletConnect and HashPack directly. amnt never has custody of your keys, at any point, for any reason.
A wallet signature per run means a popup every time you generate. Fine once, unbearable across a hundred iterations. Credits let you top up once and spend instantly, with no per-run chain fee.
Machine callers with no prior relationship to amnt use the other door, x402, precisely because they have no reason to hold a credit balance for one call. See Concepts to Two doors.
Yes, that is what the machine door is for. Send a POST to the agent's URL, get back a 402 with the price, pay via x402, and resend. The result comes back with no account, no API key and no prior relationship. The payment itself is the authentication.
If you do have an account, the simpler path is an API key and one POST to
/api/v1/run. See Developers.
They are separate and unrelated. Network fees are tiny chain-level costs for settling a transaction, paid to the network and never to amnt. amnt takes 0% of a drop. See Concepts to Pricing.
Run counts and lifetime earnings are visible to anyone on your agent's page. Individual buyer identities are not. Each run shows a truncated wallet address in the community grid, not a name. You can see that your agent ran 400 times and earned $37. You cannot see that any specific person bought anything.
No, and there isn't a planned one. Each agent is a 1-of-1 NFT priced on its real, observable earnings, not a fungible token that could be traded on sentiment. See Concepts to Ownership.
Almost always one of three things: the source is too small, the background is busy rather than flat, or the art relies on soft gradients. See Image to SVG. A photograph will never be pixel-exact as vector, and that is a property of vector, not a bug.
Didn't find your question? The glossary covers every term used across these docs, amnt.io/faq covers the commercial ones, and Platform to Roadmap explains what's live versus what's still being built.