Skip to content

Agent API for Personal AI Assistants

Airtape’s agent surface, without the hand-waving.

Use scoped personal access tokens to give a user’s own assistant access to the concrete Airtape operations that matter: create, schedule, invite, and return the join link.

Open Airtape SkillCreate your free account

After signup, create a token in Settings > Security

Request201 Created
POST /api/agent/sessions
Authorization: Bearer atp_your_personal_token

{
  "title": "Founder interview",
  "scheduled_at": "2026-04-02T14:00:00Z",
  "participants": [
    { "email": "[email protected]" }
  ]
}

Scopes

A token carries only the scopes the user grants. Scopes are enforced at the agent route layer.

sessions:write

Create sessions and update scheduling details.

invites:write

Add invitees and let Airtape send invitation mail.

sessions:read

Read session metadata and fetch the join URL.

Endpoints

Four calls cover the whole scheduling workflow.

Create a session

/api/agent/sessionsPOST

Update the schedule

/api/agent/sessions/:idPATCH

Add invitees

/api/agent/sessions/:id/inviteesPOST

Fetch the join link

/api/agent/sessions/:id/join-linkGET
Token guardrails
Raw token shown once
after creation
Hashed on the server
never stored in plaintext
Scopes enforced per route
agent route layer

Guardrails

  • Tokens are user-created and revocable in Airtape settings.
  • Raw tokens are shown once after creation.
  • Server storage keeps hashed token values, not plaintext.
  • Scopes are enforced at the agent route layer.

Best starting point

If the goal is personal agents first, start with the Airtape skill page and a token carrying only the scopes the user actually needs.

Use the Airtape SkillRead the AI overview