> For the complete documentation index, see [llms.txt](https://wiki.orbofi.com/learn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.orbofi.com/learn/aac-metadata-api/get-a-token-card.md).

# Get a token card

### Request

```bash
curl https://api.orbofi.com/v1/tokens/{tokenAddress}
```

`tokenAddress` is the agent token's address on Robinhood Chain, in any case (it is lowercased server-side).

{% hint style="info" %}
Integrations built against the earlier path — `https://server.orbofi.com/rh/token/{tokenAddress}` — keep working indefinitely; it serves the same handler. New integrations should use the canonical URL above.
{% endhint %}

### Response

```json
{
  "address": "0xa197402dea39e3d03c208319888bbd58976e6aac",
  "chainId": 4663,
  "agentId": 10307,
  "name": "Sketch Forge",
  "symbol": "SKETCHFO",
  "description": "Turns rough ideas into finished concept art.",
  "image": "https://cdn.orbofi.com/...",
  "pageUrl": "https://www.orbofi.com/agent/0xa197402dea39e3d03c208319888bbd58976e6aac",
  "website": "https://www.orbofi.com/agent/0xa197402dea39e3d03c208319888bbd58976e6aac",
  "twitter": "https://x.com/...",
  "telegram": "https://t.me/...",
  "launchedAt": 1787156829
}
```

| Field                          | Meaning                                                                                           |
| ------------------------------ | ------------------------------------------------------------------------------------------------- |
| `address`                      | The token, lowercased.                                                                            |
| `chainId`                      | Always `4663` (Robinhood Chain).                                                                  |
| `agentId`                      | Orbofi's internal agent id. Stable; useful as a foreign key.                                      |
| `name`, `description`, `image` | The agent's display card.                                                                         |
| `symbol`                       | The token's ERC-20 symbol, read from the chain. Omitted in the rare case it couldn't be read yet. |
| `launchedAt`                   | Launch time, unix seconds, from the on-chain launch record. Omitted if not yet resolved.          |
| `pageUrl` / `website`          | The token's canonical home — the agent page. Link here.                                           |
| `twitter`, `telegram`          | Creator socials, full URLs. **Omitted when absent** — don't rely on the keys existing.            |

### Semantics that matter

* **404 is uniform.** Unknown address, not-yet-published token, non-Orbofi token — all return the same `{"error":"no verified agent token at this address"}`. Treat 404 as "no card", nothing more.
* **`Cache-Control: no-store`.** Eligibility is re-checked live on every request, so a card disappears the moment an agent is made private or re-pointed. Poll freely; don't add your own long cache.
* **No auth, no rate key.** The endpoint is public by design. Be a good citizen with request volume and it stays that way.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.orbofi.com/learn/aac-metadata-api/get-a-token-card.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.