AutoQuote3D developer resources

The AutoQuote3D REST API is described by an OpenAPI document generated from the Effect HttpApi contract. Requests use an x-api-key header. After creating an AutoQuote3D account and selecting a Business, an authorized Business member can create and revoke API keys from the API Keys page in the application. Treat every key as a production credential, store it in a secret manager, and never place it in client-side code.

Generate clients from the OpenAPI URL rather than copying request shapes from screenshots or marketing pages. The contract names stable paths, request and response schemas, error responses, and the API-key security scheme. The API currently operates against live Business data; AutoQuote3D does not advertise a public sandbox.

The AutoQuote3D MCP server uses Streamable HTTP at the canonical MCP endpoint. MCP clients discover the OAuth authorization server through RFC 9728 protected-resource metadata, register a client when supported, request mcp:read for read-only tools or mcp:write for mutations, and ask the user to approve access. The legacy mcp scope grants full access for compatible existing clients. The server exposes shop workflows as MCP tools and publishes agent guidance as MCP resources.

Use MCP when an agent needs interactive access to Business context, Quotes, Orders, catalog configuration, or analytics. Read each tool description and annotations before calling it, pass the Business identifier requested by the tool, and obtain user confirmation before write or destructive operations.

AutoQuote3D does not currently advertise a general outbound public webhooks product. Integrators should not invent webhook endpoints or depend on internal payment-provider callbacks. Use the documented REST API or MCP server and contact sales@autoquote3d.com if an event-driven integration is required.

A 14-day self-service product trial is available. API keys are self-service for signed-in Business members, while MCP access uses OAuth and does not require copying an API key into the client. There is no public sandbox today, so test with a dedicated Business and non-sensitive sample records.

REST paths carry their version in the URL. Read the API lifecycle and deprecation policy before depending on a preview version, and monitor its documented Deprecation, Sunset, and Link response signals when an operation is retired.

AutoQuote3D does not currently publish an official npm, PyPI, or Homebrew CLI. For scripts, call the REST API with curl or a client generated from OpenAPI. Do not install similarly named third-party packages on the assumption that they are maintained by AutoQuote3D.