# T3OS Developer Platform

> Agent-readable entry point for https://dev.t3os.ai. This file is public; it contains no credentials or customer data.

## Start here

- [Complete T3OS integration guide](https://dev.t3os.ai/llms-full.txt): canonical text guide for coding agents. Read before designing or implementing an integration.
- [Developer portal](https://dev.t3os.ai/): app registration and developer access.
- [GraphQL reference](https://dev.t3os.ai/docs/graphql): rendered browser reference. The live GraphQL explorer is the deployed-schema authority.
- [Custom Data](https://dev.t3os.ai/docs/custom-data): custom fields, reusable custom objects, references, values, lifecycle, and GraphQL workflows.
- [T3OS UI components](https://dev.t3os.ai/docs/ui-components): interactive previews and adoption guidance for copy-owned React components.
- [Reference apps](https://github.com/EquipmentShare/t3os-examples): public OAuth, OIDC, and workspace-installed implementations.

## Canonical sources and operating rules

- Use the T3OS MCP server as the source of truth for available API capabilities, authentication requirements, and planning guidance. Do not infer API fields or server rules from this file.
- Before broad integration work, obtain a `WORKSPACE_INSTALLED` MCP planning contract with `get_t3os_planning_contract`, complete it, then call `review_t3os_plan`. Resolve its required fixes and open questions.
- Prefer `WORKSPACE_INSTALLED` plus `X-API-Key` for server-to-server or agent integrations. Use `USER_DELEGATED` OAuth only when actions must run as a specific user.
- Never include real API keys, OAuth client secrets, webhook signing secrets, tokens, customer data, or private callback material in prompts, source, logs, or plan reviews. Use placeholders.

## Machine-readable discovery

- [robots.txt](https://dev.t3os.ai/robots.txt)
- [sitemap.xml](https://dev.t3os.ai/sitemap.xml)