spectracebeta
ProductPricingDocsChangelog
Sign inStart free
Overview
Get started
  • What Spectrace does
  • Quick start
  • Core concepts
Requirements
  • Write a good requirement
  • Write acceptance criteria
  • Import requirements
  • Move a requirement through workflow stages
  • Assign a requirement and see who worked on it
Verification
  • How PR verification works
  • Linking a PR to a requirement
  • Reading a verification result
  • Check runs and branch protection
  • Spec drift
Integrations
  • Install the GitHub App
  • Use the VS Code extension
  • Connect Slack, Jira, and Linear
AI agents (MCP)
  • Connect an agent
  • MCP tool reference
  • Verify before you push
API
  • API keys
Platform
  • Security
  • Architecture
  • Roles and permissions
  • Data retention and deletion
Reference
  • Look up a term
  • Fix a common problem
  • Environment variables
  • GitHub App permissions
DocsAPI

API

API keys — how to create and revoke one, and what a key authenticates today.

For teams that integrate programmatically: today an API key authenticates the Spectrace MCP server only, and there is no public REST API or outbound webhook. This group covers creating, using and revoking API keys; for the tools a key unlocks, see AI agents (MCP).

In this section
  • API keysCreate, use, revoke and delete Spectrace API keys, and understand what a key authenticates today.
Edit this page on GitHub
PreviousVerify before you pushNext API keys
spectracebeta

The trace between specs and code. From PRD to PR, with proof.

Product

  • PR verification
  • VS Code
  • Requirements
  • Test generation
  • MCP server

Resources

  • Docs
  • Changelog
  • Architecture
  • Security

Company

  • Pricing
  • Privacy
  • Terms

© 2026 Spectrace. All rights reserved.