> 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/developer-guide/operations/reference.md).

# Reference

Technical reference for rate limits, memory architecture, terminology mapping, common patterns, and architecture decisions.

Technical reference for the Concurrence platform. Each page below answers a specific class of question - use this index to jump straight to the right one.

* [**Rate Limits**](/developer-guide/operations/reference/rate-limits.md): per-endpoint request limits, rate-limit response headers, and retry guidance. Covers Classic API endpoints.
* [**Memory Architecture & API Mapping**](/developer-guide/operations/reference/memory-architecture.md): how the Classic API's L0-L3 labels map to its endpoints, plus the separate Platform API world-model memory surface.
* [**Terminology Mapping**](/developer-guide/operations/reference/terminology-mapping.md): the translation table between platform documentation names and Classic API resource names (Context Graph vs `service_hierarchical_state_machine`, and so on).
* [**Common Patterns**](/developer-guide/operations/reference/common-patterns.md): runnable Python and TypeScript examples for conversation lifecycle, user models, webhooks, routing, and CI simulation gates. Targets the Classic API.
* [**Architecture Decision Records**](/developer-guide/operations/reference/architecture-decisions.md): why the API uses NDJSON streaming, JWT authentication, and its resource naming. Applies to both APIs where noted.

{% content-ref url="/pages/LCkfSHsnlATG4pq0VYqR" %}
[Rate Limits](/developer-guide/operations/reference/rate-limits.md)
{% endcontent-ref %}

{% content-ref url="/pages/CvKuNt4O4FVsGbHQd73K" %}
[Memory Architecture & API Mapping](/developer-guide/operations/reference/memory-architecture.md)
{% endcontent-ref %}

{% content-ref url="/pages/vXbjrzvq0D9Y63tLDE6T" %}
[Terminology Mapping](/developer-guide/operations/reference/terminology-mapping.md)
{% endcontent-ref %}

{% content-ref url="/pages/L63NLWQ0ELwHxvEclaNp" %}
[Common Patterns](/developer-guide/operations/reference/common-patterns.md)
{% endcontent-ref %}

{% content-ref url="/pages/ooKf8myoEvi9HlhzkIzf" %}
[Architecture Decisions](/developer-guide/operations/reference/architecture-decisions.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/developer-guide/operations/reference.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.