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

# API Keys

> Complete guide to managing API keys for the Nolano forecasting API

## Managing API Keys

You can manage your API keys through the Nolano dashboard.

<Card title="Go to API Keys Dashboard" icon="key" href="https://app.nolano.ai/dashboard/api-keys">
  The dashboard provides an easy-to-use interface for all your API key management needs.
</Card>

## What are API Keys?

API keys are unique identifiers that authenticate your requests to the Nolano API. They act as both an identifier and a password, ensuring that only authorized users can access forecasting services and manage API resources.

## Key Features

### Secure by Design

<CardGroup cols={2}>
  <Card title="SHA-256 Hashing" icon="shield-check">
    Keys are hashed before storage - original keys are never stored in plain text
  </Card>

  <Card title="Usage Tracking" icon="chart-bar">
    Every API call is logged with detailed usage statistics and monitoring
  </Card>

  <Card title="Expiration Control" icon="clock">
    Set custom expiration dates or create keys that never expire
  </Card>

  <Card title="Instant Revocation" icon="x-mark">
    Immediately revoke compromised keys with audit trails
  </Card>
</CardGroup>

### Storage and Handling

<Warning>
  **Never expose API keys in client-side code**: API keys should only be used in server-side applications where they can be kept secure.
</Warning>

<Note>
  **Environment Variables**: Store API keys in environment variables, not in your source code.
</Note>

```bash theme={null}
# ✅ Good: Environment variable
export NOLANO_API_KEY="ak_577aa2f186866ec0c75d1068bcff79cd3da4344b80aec1572e0fa07b364227d6"

# ❌ Bad: Hardcoded in source
api_key = "ak_577aa2f186866ec0c75d1068bcff79cd3da4344b80aec1572e0fa07b364227d6"
```

### Regular Rotation (Coming soon)

Implement a regular key rotation schedule:

1. **Production Keys**: Rotate every 90 days
2. **Development Keys**: Rotate every 30 days
3. **Emergency Rotation**: Immediately if compromise suspected

## Rate Limits by Key Type

| Permission Level | Requests/Min | Requests/Hour | Requests/Day |
| - | - | - | - |
| **Read Only** | 50 | 500 | 10,000 |
| **Read/Write** | 100 | 1,000 | 50,000 |
| **Admin** | 200 | 2,000 | 100,000 |
| **Full Access** | 500 | 5,000 | 250,000 |

<Tip>
  **Enterprise Plans**: Custom rate limits and dedicated support available. Contact [hello@nolano.com](mailto:hello@nolano.com) for details.
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.