Quickstart structure
How a future guide could move from project setup to one verifiable request.
Documentation
Local interface preview with sample data. The examples use a reserved address and are not a live service, SDK guide, or public contract.
Sample quickstart layout
- 01Create a sample project
Review the interface without issuing a credential.
- 02Inspect a request shape
Use non-routable examples that cannot be mistaken for access.
- 03Tie docs to a release
Publish real instructions only with a supported artifact.
# Non-executable interface sample
curl https://example.invalid/v1/responses \
-H "Authorization: Bearer SAMPLE_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"sample-research","input":"Hello"}'Guide structure
Request and response shape
How fields, errors, and state could be explained without implying a live contract.
Release notes
How changes, limits, and support windows would need to be tied to actual releases.
No live developer documentation is published.
A real documentation release requires a supported service, exact request behavior, current limits, change policy, and a support path.