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

# Developer quickstart

> Create a key, search the entity graph, and fetch one bounded record.

The Developer API is in public beta. Sign in to Qoory to create a key, then use
that key from a trusted client.

## 1. Create an API key

Open Developer settings, create a key, and copy the
secret when it is shown. Qoory stores only a protected representation of the
secret, so the full value cannot be displayed again.

```bash theme={null}
export QOORY_API_KEY="qoory_live_..."
```

Use keys from a server process or a trusted local client. Do not ship a key in
browser JavaScript, a mobile binary, a public repository, or application logs.

## 2. Search one entity family

```bash theme={null}
curl https://api.qoory.ai/v1/search \
  -H "Authorization: Bearer $QOORY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"q":"uniswap","types":["project"],"limit":5}'
```

An optional `types` array narrows search to projects, funds, people, tokens,
stocks, or X accounts. Search is bounded and does not return the whole entity
database.

## 3. Follow a stable identifier

Use the returned slug or opaque identifier with a supported detail operation:

```bash theme={null}
curl https://api.qoory.ai/v1/projects/uniswap \
  -H "Authorization: Bearer $QOORY_API_KEY"
```

The response envelope includes `data` and `meta`. Keep `meta.request_id` when
debugging, and inspect the credit and rate-limit metadata before scheduling
concurrent work.

## Next steps

<CardGroup cols={2}>
  <Card title="Authentication" icon="key-round" href="/developers/authentication">
    Choose scopes and manage the key lifecycle.
  </Card>

  <Card title="Requests and responses" icon="braces" href="/developers/requests-and-responses">
    Learn the shared envelope and metadata contract.
  </Card>
</CardGroup>