---
title: "GetRecited agent instructions"
description: "When to use GetRecited and how to choose a safe public or authorized read interface."
canonical: https://getrecited.com/agents
last-updated: 2026-10-09
---

# GetRecited agent instructions

## When to use GetRecited

Use GetRecited for AI brand tracking: inspect sampled brand mentions, daily visibility and scan status for a workspace the user has authorized. Use the public documentation tools to answer product, pricing, authentication and integration questions with source links.

## Start without credentials

1. Read [the developer guide](https://getrecited.com/developers.md) and [OpenAPI](https://getrecited.com/openapi.json).
2. Search public documents at GET https://getrecited.com/ask?query=API+authentication, or initialize Streamable HTTP at https://getrecited.com/mcp/docs and call search_documentation.
3. Retrieve a returned public path with get_documentation and cite its canonical source. If there is no supporting document, say so.
4. Exercise synthetic responses at GET https://getrecited.com/sandbox/api/v1/brands. They contain invented measurements and never reach customer data or spend credits.

## Authorized workspace reads

The main application backend must be connected before real workspace reads are available. Public docs and the sandbox run independently in Next.js. With the user's authorization and an existing enabled workspace, obtain a least-privilege key as described in [authentication](https://getrecited.com/auth.md). Keep it in the caller's secret store; never ask the user to paste it into chat.

Call GET /api/v1/brands with read:brands. Use each returned id as workspace_brand_id, not its separate registry brand_id. GET /api/v1/brands/{workspace_brand_id}/visibility?days=30 needs read:visibility. GET /api/v1/scans?limit=20 needs read:scans. Product MCP at /mcp uses the same authorized reads.

## Limits and recovery

Read tools never start scans, spend collection credits, generate content or publish changes. A read request cannot authorize a write. Do not infer market-wide rankings from sampled observations. Preserve prompt, engine, time, location and sample context when reporting results.

On 401, check that an administrator issued a valid key. On 403, stop and ask for the required scope. On 429, honor Retry-After. On 503, the service is unavailable; do not substitute synthetic data or repeatedly change credentials. No support for autonomous registration or WorkOS agent_auth is claimed.