FAQ
Answers to the questions that come up once someone actually uses amnt.
Unlock buys you 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 entire product depends on the recipe staying secret regardless of who's paid for what. See Buyers → Unlock & ownership.
Image count is a setting the creator locks at publish, never something a buyer chooses per run. If it were buyer-controlled, someone could request ten images at a one-image price and the run would cost more to fulfil than it earned — every time. If you want more than one result from an agent, look for its Unlock option instead. See Concepts → Pricing.
Ownership is resolved live, at the moment each payment settles — never cached from an earlier lookup. If an agent sells between two of your calls, the second call's payment correctly goes to the new owner. See Concepts → Ownership.
No. Everything is priced in USD — credits, costs, and the price floor itself — specifically so a swing in HBAR's exchange rate can't silently erode a creator's margin. See Platform → Money rules.
Below roughly 3×, thin margins get eaten by the ordinary variance in provider costs and occasional refunded failures — an agent priced right at cost is one bad week away from losing money on every run. 3× measured cost, with a $0.02 absolute floor for very cheap outputs, is the number that holds up across both a $0.002 text run and an $0.80 image batch.
Some wallets don't automatically accept a new token type the first time one is sent to them. If yours doesn't, your NFT waits as a pending gift rather than the platform quietly pretending it arrived — the agent page will tell you it's waiting and how to claim it.
Yes, but an edit creates a new version rather than silently changing what's already live. Anyone who unlocked the recipe, or any code integrated against a specific version, keeps the behaviour it was built against. See Creators → Publishing.
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 from then on, with no per-run chain fee. Machine callers with no prior relationship to amnt use a different door — see Concepts → Two doors — precisely because they have no reason to hold a credit balance for one call.
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 per agent that could be traded on sentiment. See Concepts → Ownership for the full reasoning.
An agent is automatically suspended when its failure rate goes above 20% over its last 50 runs — the platform does this without waiting for anyone to notice, because a broken agent burns money and produces nothing for buyers. The suspension is visible on your agent's page.
The fix is to look at what changed: check whether a provider setting is now out of range, whether a slot is accepting values your recipe can't handle, or whether the model itself changed behaviour. Edit the agent (which creates a new version), test the recipe again in the Studio, and republish. The new version starts from a clean suspension record.
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 (0.0.12…) in the community grid, not a name. You can
see that your agent ran 400 times and earned $37. You can't see that any
specific person made a purchase.
Yes. That's exactly what the machine door is for. Send a POST to the
agent's URL with your slot values, get back a 402 with the price, pay
via the x402 protocol, and resend — the result comes back with no
account, no API key, and no prior relationship with amnt required. 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 the developer docs.
They're separate and unrelated. Hedera network fees are tiny chain-level costs for settling a transaction on the ledger — typically fractions of a cent, paid to the network, never to amnt. amnt's platform fee is 25% of each run's profit (not its gross price), paid to the platform for running the infrastructure. The two numbers don't overlap; one goes to the ledger, one comes to amnt. See Concepts → Pricing for the full split breakdown.
Didn't find your question? The glossary covers every term used across these docs, and Platform → Roadmap explains what's live versus what's still being built.