# Workflows

Hosted API users do not create keys directly through admin endpoints.

Use this workflow to request access credentials.

## 1. Request access

Submit your access request through Ardent Research [onboarding channel](https://www.ardentresearch.xyz/#waitlist).

Recommended request details:

1. Primary technical contact email.
2. Project, team or company name.
3. What you're building or intended use case (feel free to include expected request volume and preferred payment mode).

## 2. Receive credentials

After approval, the Ardent Research team provides your API key securely.

Store it immediately in your secret manager.

## 3. Configure your environment \[optional]

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

## 4. Verify key quickly \[optional]

```bash
curl -G "$BASE_URL/wallet" \
  -H "X-API-Key: $API_KEY" \
  --data-urlencode "agent_id=integration-smoke-test" \
  --data-urlencode "chain=ethereum"
```

A successful response confirms your key is active.

## 5. Rotation and recovery

If your key is exposed or lost, request rotation through the same onboarding or support channel.

For broader Sepolia setup details, see [Testnet Guide](/testnet-guide.md).

## 6. Request aUSD separately on testnet

`aUSD` requests are handled through a separate faucet form, not the onboarding form.

The only required field in the faucet request is your agent smart wallet address.

Use this process:

1. Call `GET /wallet` to get your agent smart wallet address.
2. Submit that wallet address in the aUSD faucet request form.
3. Wait for allocation confirmation, then continue with simulate and execute tests.

Faucet link:

`https://faucet.ardentresearch.xyz`


---

# Agent Instructions: 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:

```
GET https://docs.ardentresearch.xyz/request-api-key.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.