Developer platform

Build on the execution layer.

The Airspeed API gives you programmatic access to every conversation, playbook, and agent run, so you can pull revenue intelligence into your own tools, dashboards, and automations.

Get API access → See the use cases API reference 
# every conversation, structured
$ curl "$AIRSPEED_API/calls/" \
    -H "X-API-Key: $AIRSPEED_API_KEY"

# every agent run, with its structured output
$ curl "$AIRSPEED_API/agent-runs/" \
    -H "X-API-Key: $AIRSPEED_API_KEY"
Why build here

Build on a strong revenue foundation.

Go 0 to 1 faster

Every call, playbook, and agent run is already captured, structured, and queryable. Start from data, not plumbing.

Skip the maintenance

Airspeed manages recording, transcription, extraction, and CRM sync reliability, so you do not inherit the upkeep.

Governance built in

Permissions, playbook logic, and CRM sync controls live in Airspeed, not in scripts scattered across your stack.

Use case 01 · Revenue data

Pull conversation intelligence into your stack.

Read calls, transcripts, snippets, and extracted fields into your data warehouse, BI, or CRM automations. It is the same structured data the agents run on, exposed as plain REST resources.

Get API access →

# calls in your workspace, with extracted fields
curl "$AIRSPEED_API/calls/" \
  -H "X-API-Key: $AIRSPEED_API_KEY"

# key moments from one conversation
curl "$AIRSPEED_API/calls/$CALL_ID/snippets" \
  -H "X-API-Key: $AIRSPEED_API_KEY"
Use case 02 · Agent output

Read every agent run into your systems.

Every agent run lands as structured output you can list and fetch by ID. Pipe results into dashboards, QA reviews, or your CRM, and audit what the agents did and when.

Get API access →

const res = await fetch(`${API}/agent-runs/`, {
  headers: { "X-API-Key": key }
})
const runs = await res.json()

// one run, with its structured output:
// GET /v1/agent-runs/{run_id}
Use case 03 · Playbook logic

Sync the criteria agents score against.

Playbooks define what good looks like: the criteria agents score deals and calls against. Pull definitions and version history into enablement docs, review flows, or your own analytics.

Get API access →

# playbook definitions
curl "$AIRSPEED_API/playbooks/" \
  -H "X-API-Key: $AIRSPEED_API_KEY"

# version history for one playbook
curl "$AIRSPEED_API/playbooks/$PLAYBOOK_ID/versions" \
  -H "X-API-Key: $AIRSPEED_API_KEY"
API reference

Core resources.

The same objects the agents and the Airspeed MCP extension are built on. Send your API key in the X-API-Key header, then call any resource. Two minutes to your first response. 

# keys live in Settings, then Developer
export AIRSPEED_API_KEY="<your-api-key>"
export AIRSPEED_API="https://api.glyphic.ai/v1"

curl "$AIRSPEED_API/calls/" \
  -H "X-API-Key: $AIRSPEED_API_KEY"
  • Calls /v1/calls/ Conversations with extracted fields, plus snippets and recording media per call.
  • Call tags /v1/call_tags/ The tag taxonomy used to classify conversations.
  • Playbooks /v1/playbooks/ Playbook definitions and version history, the criteria agents score against.
  • Agent runs /v1/agent-runs/ Status and structured output of every agent run.

The full endpoint reference is generated from the live routes, so it never drifts from what ships. Full API reference →

Developer platform

Start building.

Get an API key and pull the execution layer into your own stack.

Get API access →

Explore Airspeed

Most AI sales tools tell you what happened on the call. Airspeed does the work after it: your pipeline worked, your CRM updated, your reps coached, your forecast called.