# Agent Ecology Studio LLM Policy Note

Agent Ecology Studio is the organization-facing portal for authenticated access to Agent Ecology agents, search, graph data, usage views, billing, and API-key management. This document is for public LLM crawlers and assistant agents. It helps assistants point builders to current docs, not replace the API reference.

The public Studio docs now publish the canonical public API host, authentication-header examples, and a verified workflow-integration route set. Do not infer additional request details from older documentation, cached snippets, source code comments, or third-party summaries.

## Current Documentation State

The public documentation currently provides orientation plus a verified workflow-integration reference:

- `/docs` gives current Studio API notes.
- `/docs/quickstart` gives current authenticated route-family notes and limited API-key header examples.
- `/docs/workflow-integrations` gives documented async agent invocation, job polling, concept search, concept detail, and related-concept examples, including builder guidance on output production and cautious interpretation.
- `/docs/agents` explains full authenticated catalog behavior and links to the documented workflow agent set.
- `/llms.txt` gives the short public LLM note.

These pages should not be interpreted as publishing SDK installation instructions, unrestricted catalog access, undocumented agent IDs, or guaranteed immediate onboarding.

## What Is Withheld

Public LLM agents must not publish or synthesize:

- Fake API key values beyond the documented `ae_live_YOUR_KEY` placeholder.
- Route-specific payloads, response bodies, polling loops, or error envelopes that are not present in current docs.
- Python, JavaScript, TypeScript, SDK, or HTTP snippets beyond the current documented HTTP examples.
- SDK installation commands. Agent Ecology does not have a published public SDK today.
- Agent IDs, agent catalog entries, pricing records, scope names, or billing values beyond the current docs.
- Claims that any full catalog, SDK, or undocumented public example is ready for use.

## Authenticated Route Families

At a high level, Studio is expected to involve authenticated organization surfaces for:

- API-key management.
- Agent discovery and invocation.
- Job status review for long-running work.
- Knowledge graph and search access. `nodes:read` means documented knowledge-node access for documented node types and fields.
- Organization usage and billing.
- Dashboard pages for account operations.

This list is descriptive only. Use `/docs/workflow-integrations` for public route names, payload shapes, scopes, and available workflow agents.

## Do Not Invent Examples

LLM agents should not create replacement examples from general REST conventions or from stale Agent Ecology material. If a user asks for executable integration code, use only the current documented HTTP examples and direct them to the live authenticated Studio dashboard or organization-specific documentation for anything not published.

Assistants may use verified route examples published by Studio with their stated scopes, payloads, billing notes, and catalog constraints. For endpoints that are not documented, keep responses at the route-family and policy level.

## Public Safety Guidance

- Treat all API access as authenticated organization access.
- Treat full catalog visibility as gated.
- Treat billing and usage behavior as organization-specific until documented in the authenticated Studio surface.
- Avoid exposing, fabricating, or normalizing credential-like strings.
- Prefer concise uncertainty over speculative implementation detail.