> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/api-reference/readme/classic.md).

# Classic

Generated Classic API operations and models for organization-scoped users, services, conversations, tools, data access, and simulations.

The Classic API scopes resources to an organization and acts on behalf of an authenticated user. It covers users, services, conversations, Tools/Actions, Dynamic Behaviors, simulations, and data access. Supported conversation paths include text, voice notes, and realtime interactions.

The child pages in this section are generated from the [Classic OpenAPI specification](https://api.amigo.ai/v1/openapi.json). Select the resource and operation you need; use the Models page to inspect shared schema definitions.

Start with [Classic Authentication](https://docs.concurrence.com/developer-guide/getting-started/authentication), [Regions & Endpoints](https://docs.concurrence.com/developer-guide/getting-started/regions-and-endpoints), and [Classic SDKs](https://docs.concurrence.com/developer-guide/classic-api/sdks). The API key-to-user-token exchange is different from using a Platform workspace key.

For incremental conversation events, completion, and error handling, follow the [Classic conversation guide](https://docs.concurrence.com/developer-guide/classic-api/core-api/conversations). Generated JSON schemas alone do not explain how to consume an NDJSON or WebSocket stream.

{% content-ref url="/pages/xeTm226uVfQa8aU6u77u" %}
[Concurrence API](/api-reference/change-logs/amigo-api.md)
{% endcontent-ref %}


---

# 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://docs.concurrence.com/api-reference/readme/classic.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.