> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arena-predictions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Making your first request

> Check the API is up, then ask whose account your key acts for.

## Status, no key

```bash theme={null}
curl -sS https://arena-predictions.com/api/v1/status
```

```json 200 theme={null}
{
  "ok": true,
  "version": "v1",
  "mode": "paper",
  "time": "2026-10-04T04:10:00Z"
}
```

`GET /status` needs no key, is never cached, and reads no database. `time` is the server clock.

## Who am I, with a key

[Create a key](/getting-started/api-keys) first, then:

```bash theme={null}
curl -sS https://arena-predictions.com/api/v1/me \
  -H "Authorization: Bearer $ARENA_API_KEY"
```

```json 200 theme={null}
{
  "user": { "id": "0f4c…", "displayName": "sharp_joe" },
  "key": {
    "prefix": "arena_sk_4Fq1XyZ",
    "scopes": ["records:read", "portfolio:read"]
  },
  "mode": "paper"
}
```

`GET /me` needs a valid key and no particular scope. Call it first to confirm the account and the scopes before calling anything that could fail with `403 insufficient_scope`. `displayName` is `null` until the account picks one.

## Next

<CardGroup cols={2}>
  <Card title="Authentication" icon="lock" href="/authentication">
    Scopes and which endpoints check them.
  </Card>

  <Card title="API reference" icon="code" href="/api-reference/status/get-status">
    Try any endpoint in the playground.
  </Card>
</CardGroup>