agt_*) to have the money it moves attributed to it, then give it a key.
Before you start, connect Natural to your agent or create an API key. See Start here. Setup takes a couple of minutes; the MCP path needs no API key.
If an MCP host is operating Natural for you, use the MCP example. The linked API reference has
per-language samples and a playground.
Create the agent
Create an agent withPOST /agents.
name is up to 32 characters and description up to 100. limits takes perTransaction, perDay, and perMonth in integer cents. Pass walletId to choose the wallet the agent spends from; omit it and Natural attaches your default wallet. Natural derives the agent’s handle slug from its name; to claim a specific slug, see Claim a handle.
The response carries the agent’s ID (agt_*). Attribution comes from the agent’s key, not from a request field; issue a key next.
Issue a key
Creating an agent returns its ID, not a credential. Issue a key next so your runtime can authenticate as that agent withak_ntl_*. Over the API you call POST /agent-keys next; the dashboard does both steps for you.
agentKey:
$NATURAL_USER_TOKEN in the cURL example is that session credential, the same one natural login stores for the CLI. The full secret is returned once, so store it in your secrets manager immediately. Afterward you can see only its prefix.
To list, rotate, or revoke keys on an existing agent, see Manage your agents. For every field and status of an agent, see The Agent object.