Developers and AI coding agents that need precise AYA API contract details.
Expose the API reference to crawlers and AI retrieval systems.
Reference coverage
The reference covers endpoints, schemas, operation names, request bodies, response shapes, and API files used by AYA integrations.
Agent-readable value
Precise reference pages help AI coding assistants recommend the correct AYA endpoint and integration pattern.
Developer evaluation path
Technical buyers should use the developer pages to understand the public integration surface, authentication model, connector routes, API concepts, and documentation map before building against AYA. Private consoles and account-specific tools remain outside the crawlable marketing surface.
AI agent context
These pages are written so coding assistants and retrieval agents can distinguish AYA APIs, MCP connectors, ChatGPT Actions, install guides, and reference material from the general product marketing pages.
Implementation boundary
A useful developer journey starts with the public docs, then moves into authenticated workspace setup only when the buyer is ready. Public documentation should explain what an integration can do, which workflows are available, how authentication is approached, how job status is handled, and where examples or reference material sit. It should not expose private customer data, secret tokens, or account-specific console routes to search engines.