REST API

The Assemble REST API lets external agents and integrations push draft artifacts into a workspace and search or fetch validated artifacts.

Base URL

https://poc.assemble.site.avrdevelopment.com/api/v1

Authentication

Every request is authenticated with a workspace API key passed as a Bearer token:

curl "https://poc.assemble.site.avrdevelopment.com/api/v1/artifacts?query=churn" \
  -H "Authorization: Bearer <your-api-key>"

Create keys in Settings → API Keys. A key is scoped to one workspace — it can only read that workspace's intelligence and push drafts into it.

Keys can optionally carry capability scopes (artifacts:read, artifacts:write, intelligence:read, data:read, skills:read). A key without scopes has full access; a key with scopes is limited to them and gets 403 elsewhere — use scoped keys for partners who should, say, push artifacts but not read your data map.

The intelligence loop

The API is designed for external agents that want to make decisions the way your workspace does:

1. Read before deciding — GET /briefing (context, directives, rules), GET /memories?query= (semantic recall), GET /data-sources and GET /data-sources/{name}/query-intelligence (schemas, gotchas, proven SQL), GET /skills (procedures).
2. Write back — POST /artifacts creates drafts for human validation.
3. Learn from outcomes — GET /feedback returns what humans validated or disputed (and why), so your agent can self-correct.

Drafts and validation

Artifacts pushed through the API are created with status: "draft". A human reviews and validates them in Assemble before they become part of the workspace's searchable intelligence — so external contributions never silently become "truth" for other consumers.

OpenAPI specification

The machine-readable spec is served at /api/v1/openapi.json. It is generated from the same schemas that validate requests, so it is always current. Use it to generate clients or to wire the API into agent tooling.

Looking for the MCP integration instead? See MCP Server.