Assistants and API

Access boundary: Qualified assistant host required.

Implemented contracts/packages; actual host compatibility, OAuth and marketplace publication need separate evidence.

Surfaces: Web guides, REST/OpenAPI, MCP and host-specific installation packages.

Read the engineering guide · All features

Capabilities

1. Discover actual account capabilities and limits
2. REST/OpenAPI and Streamable HTTP MCP catalogues
3. ChatGPT, Claude web/Desktop/Code, Grok web/Build, Cursor and Copilot installation guides; OAuth qualification is per surface
4. Import through the file transport actually supported by the host
5. Document, template, dataset, generation and preparation tools
6. Browser review before sending; scopes never elevate membership rights
7. Optional bounded expert delegation for one OAuth client
8. Complete review replaces the previous token for this dispatch/connection; review_dispatch declares destructiveHint true
9. Only a browser administrator grants/revokes a mandate
10. Six portable package workflows with English metadata, deterministic archives and inventory checks; portal review/publication remains separately evidenced
11. Manual host-specific installation packages; downloading grants no OAuth consent
12. Exact registered callback/client per host; DCR/CIMD advertising alone never proves installation
13. Explicit MCP annotations disclose overwrites, archival, sharing revocation, generation cancellation, review-token replacement and batch freezing
14. Every advertised tool has four annotation booleans and per-tool evidence, audited through actual tools/list
15. readOnlyHint/idempotentHint remain false where successful production calls persist visible connection activity; the side effect is disclosed centrally
16. Assistant restrictions cover files, text, templates, datasets, records, existing PDFs/reports; person-redacted recovery adds no automatic classification or new server guard
17. Single source version synchronises application, serverInfo and release/package manifests; builds reject version/connection drift
18. MCP bodies limited to 2 MiB and 120,000 elements; existing 100,000-cell business limit remains
19. Reproducible standalone Claude Code and relative-source local marketplace archives; six workflows without OpenAI metadata or tool preauthorisation
20. Developer guidance distinguishes canonical REST/MCP resource/issuer from optional browser Auth0 domain

REST operations

• GET /api/capabilities

Read the REST integration guide for authentication, errors and contract discovery.

MCP tools

• get_capabilities
• get_expert_status

Read the MCP integration guide for scope, approval and host boundaries.