Create a named agent connection in your workspace under Account & API access. Choose its projects and whether it can append records. Each token expires after 90 days and can be revoked.
Ask for context over HTTP.
GET https://asip.ca/api/v1/events
?project=github.com/owner/project&query=deployment
Authorization: Bearer <your ASIP token>
Your ASIP token controls which account and projects the agent can read. Cloud access requires an active trial or subscription. Existing founder accounts retain access.
Or connect through MCP.
The cloud endpoint is https://asip.ca/mcp. It accepts
authenticated Streamable HTTP JSON requests. Configure the
Authorization header in your client’s supported connection settings.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "asip_recall",
"arguments": {
"project": "github.com/owner/project",
"query": "what was verified"
}
}
}
Cloud tools: asip_status, asip_projects,
asip_recall, asip_connections, and
asip_record for connections granted write access. Native
Beacon plugins continue to record locally and recall the synchronized
history.
Follow the record to its source.
| Endpoint | What it returns |
|---|---|
GET /api/v1/me |
Authenticated account and workspace |
GET /api/v1/projects |
Projects, repositories and activity counts |
GET /api/v1/events |
Searchable history with query, project, session, agent and category filters |
GET /api/v1/sessions |
Native agent sessions and activity |
GET /api/v1/events/:id/source |
Original canonical record, checked against its SHA-256 |
GET /api/v1/relationships |
Explicit and shared-session project relationships |
GET /api/v1/connections |
Named connection metadata and owning computers |
POST /api/v1/events |
Append immutable records with write permission |
Events preserve their original IDs, time, agent, native session,
project, kind, summary, and evidence. Repeating an identical record is
safe. Reusing its ID with different content returns HTTP 409. Query
results include a next cursor; pass it as
before for the next page.
Keep the scope clear.
Cloud connections access the owner’s account and assigned projects.
Provider credentials are never returned by the cloud API. A connection
named github.work still runs provider requests through
the Beacon holding that credential.