Support
Account questions, API errors, billing, key rotation, privacy requests, and reports about supplier data handling. This is also the address to use to register a dedicated OAuth application so that grants display your product name instead of the public CLI client.
Sales and capacity
Inference capacity for a specific workload: high volume, latency-sensitive, private, region-constrained, or custom-model. Requests submitted through Terminal reach the same team.
Terminal
Submit a structured capacity request. Terminal is separate from the Grid app: it does not create a Grid account and it does not replace signup.
Documentation
Product and API documentation. Every page has a Markdown twin at the same URL with a .md suffix, and any page answers a natural-language question when you append ?ask= to its Markdown URL.
GitHub
Open-source tooling, including the Grid CLI and the AgentSea launcher.
For agents
Agents should try the machine-readable surfaces before opening a support thread: llms.txt for orientation, openapi.json for the API contract, GET /v1/models for the live instrument catalog and prices, and GET /v1/oauth/scopes for the permissions a client may request. None of them require an account.
- llms.txt — Orientation map: what The Grid is and which surface answers what.
- openapi.json — Consumption, Trading, and Platform API contracts with OAuth scopes.
- MCP server — Streamable HTTP, read-only tools for instruments, prices, and the docs.
- brand-facts.json — Structured identity, product, and API facts.
- OAuth metadata — RFC 8414 discovery for the device flow, including every named scope.
Company
Grid Markets LLC, built by Spectral Labs. United States. Agreements with The Grid are governed by the laws of Delaware, United States, as set out in the Terms of Use. How we handle personal data is described in the Privacy Policy.