> For the complete documentation index, see [llms.txt](https://docs.ardentresearch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ardentresearch.xyz/getting-started.md).

# Getting Started

This section helps you complete a first successful integration quickly.

## 1. Prepare required values

Set these shell variables in your terminal.

```bash
BASE_URL="https://api.ardentresearch.xyz"
API_KEY="ak_your_api_key"
```

If you do not have an API key yet, request access first using the onboarding channel.

See [Request API Key](/request-api-key.md).

## 2. Understand endpoint groups

The hosted API has two endpoint groups for users.

1. Public endpoints.
   1. `GET /health`
   2. `GET /feed/recent`
2. Protected API key endpoints.
   1. `GET /wallet`
   2. `GET /wallet/balance`
   3. `POST /simulate`
   4. `POST /execute`
   5. `GET /status/:id`

## 3. Understand your payment mode

Payment mode is assigned to your key by Ardent Research during access provisioning.

1. `manual`: requires payment proof for payable execution.
2. `auto`: platform performs an internal token transfer if proof is not provided.
3. `sponsored`: no external payment requirement for execution.

Detailed behavior is in [Payment Modes](/payment-modes.md).

## 4. First end to end path

Use this sequence for first validation.

1. Request API key access.
2. Choose an `agent_id` — any stable string you pick, such as `my-agent-001` or `trading-bot`. No registration needed; the platform provisions a smart wallet automatically on first use.
3. Get wallet address for your agent ID.
4. Fund wallet if your strategy needs tokens.
5. Simulate execution.
6. Execute transaction.
7. Poll status until terminal state.

You can run every step with raw curl or with the `ardent` CLI. See [Agent Integration](/agent-integration.md) for the one-line installer and CLI reference.

## 5. Terminal states

A request eventually reaches one of these terminal states.

1. `confirmed`
2. `reverted`
3. `failed`

## 6. Supported chain names in request payloads

Use one of:

1. `ethereum`
2. `base`
3. `arbitrum`

Aliases like `eth` and `arb` are accepted by server side chain parsing, but using canonical names is recommended for clean client code.

## 7. Testnet token details for Sepolia users

Current x402 payment tokens in the hosted Sepolia-family testnet environment:

| Payload chain | Test network     | USDC                                         | aUSD                                         |
| ------------- | ---------------- | -------------------------------------------- | -------------------------------------------- |
| `ethereum`    | Ethereum Sepolia | `0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238` | `0xE9df660c675F6f649677Ae408FCf6665D4F0F5Be` |
| `base`        | Base Sepolia     | `0x036CbD53842c5426634e7929541eC2318f3dCF7e` | `0xE9df660c675F6f649677Ae408FCf6665D4F0F5Be` |
| `arbitrum`    | Arbitrum Sepolia | `0x75faf114eafb1BDbe2F0316DF893fd58CE46AA4d` | `0xE9df660c675F6f649677Ae408FCf6665D4F0F5Be` |

Circle faucet USDC is available at `https://faucet.circle.com`; select the matching Sepolia network before funding. Ethereum Sepolia may also accept `USDT` at `0xd077A400968890Eacc75cdc901F0356c943e4fDb` when enabled for your environment.

For approved testers, `aUSD` (Ardent USD) is accepted in the hosted testnet payment flow and is requested through a separate faucet flow.

For exact payable amounts, always use `required_amount_raw` from the live `402 Payment Required` response.

For complete testnet instructions, see [Testnet Guide](/testnet-guide.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ardentresearch.xyz/getting-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.