Context

Every route requires an API key and an organization selected through org_id when the key can access more than one organization. The feature must be enabled for that organization. Read routes accept scope=org (the default) for the selected organization's Context and scope=global for the shared catalog; global scope never grants write access. Discover object types before reading, because the registry defines the filters, ordering, and embedded relationships for each type. Relationship tables such as product-personas are not object types: requesting one returns 400 with the embed that carries its rows.

In the web app, ask the AX Agent to research Context in chat. Conversations are private to the member who started them. Old product import links permanently redirect to your organization's Products list. Previously saved Context objects, experiments and reports remain available on their own pages and through their existing APIs. Company import is retired. Saved Companies remain available.

Connect RPC

Connect clients call POST /rpc/axp.v1.AxpContextService/<METHOD> with a Bearer API key, JSON request body, and Connect-Protocol-Version: 1. Request fields use lower camel case and every Context service response wraps the corresponding REST result in {result: ...}.

curl -X POST \
  -H "Authorization: Bearer $AX_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Connect-Protocol-Version: 1" \
  -d '{"orgId":"'$AX_ORG_ID'","scope":"global"}' \
  "https://app.514.ax/rpc/axp.v1.AxpContextService/ListContextObjects"

type is the Context object type from ListContextObjects, the same value the REST path calls {kind}. scope defaults to org; use global for the shared catalog. filters is a map of the object type's filterColumns to values. Reuse a pageToken only with the same organization, scope, type, filters, and ordering.

Claims use the separate axp.v1.AxpContextClaimsService with its single ManageContextClaim method. Its request accepts orgId, action, kind, and id, plus the action-specific claim fields; its response is also {result: ...}. Follows use axp.v1.AxpContextFollowsService with GetContextFollowState, FollowContext, and UnfollowContext; each takes kind, id, and an optional orgId and returns {following: boolean} for the authenticated person only.

GET /api/v1/context/objects

Discover the Context object types for one scope.

curl -H "Authorization: Bearer $AX_API_KEY" \
  "https://app.514.ax/api/v1/context/objects?org_id=$AX_ORG_ID&scope=global"

The response lists each object type's category (root, subobject, document, or tag), filterColumns, sortColumns, summaryColumns, and relationships: the key, object type, cardinality, and shape of every related object that GET /context/{kind}/{id} embeds. Object types that accept tags report taggable: true and a tagFilter describing the filter.tags parameter. Roots are companies, products, use-cases, personas, and agents. The companies root holds Company Context objects: the companies, customers, vendors, and competitors a workspace tracks, shown as Companies in the platform.

GET /api/v1/context/{kind}

List Context objects of one type as flat rows. Organization reads return newest updates first; shared-catalog reads are ordered by id. Use exact filter.<COLUMN>=<VALUE> parameters only for the type's filterColumns. On taggable types, filter.tags=<TAG_UUID>,<TAG_UUID> (up to 20 ids from the same scope) returns objects carrying any of those tags. Reuse next_page_token with the same organization, scope, type, filters, and ordering.

curl -H "Authorization: Bearer $AX_API_KEY" \
  "https://app.514.ax/api/v1/context/product-versions?org_id=$AX_ORG_ID&scope=global&filter.product_id=<PRODUCT_UUID>"

limit defaults to 50 and accepts 1 through 100. The response is {rows, next_page_token}.

GET /api/v1/context/{kind}/{id}

Read one Context object by UUID with its related objects embedded one level deep.

curl -H "Authorization: Bearer $AX_API_KEY" \
  "https://app.514.ax/api/v1/context/products/<CONTEXT_UUID>?org_id=$AX_ORG_ID&scope=org"

The response is the object's row plus one key per relationship from GET /context/objects: an array for many-valued relationships and an object or null for a parent. Items reached through a relationship table carry a link object with the link id and its metadata. Each array holds at most 100 items; truncatedRelationships names any that were cut. With scope=global the related objects come from the shared catalog, and archived shared roots stay readable with their revision, archived_at, and archived_by state. An archived organization root reads the same way, with archived_at and archived_by set and its archived relations left out of the embeds.

GET /api/v1/context/{kind}/{id}/documents

List documents attached to a supported host: companies, products, use-cases, personas, agents, persona-agents, interfaces, capabilities, user-flows, product-categories, product-packages, product-versions, product-competitors, agent-versions, or models.

curl -H "Authorization: Bearer $AX_API_KEY" \
  "https://app.514.ax/api/v1/context/products/<CONTEXT_UUID>/documents?org_id=$AX_ORG_ID&scope=global"

The response is {rows:[{link,document}], next_page_token}. Attachment pagination is bound to the scope, organization, host type, and host ID.

POST /api/v1/context/mutations

Edit organization-owned Context with an action/input envelope. Global Context is read-only on this route.

curl -X POST \
  -H "Authorization: Bearer $AX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"mutate","input":{"kind":"products","operation":"create","values":{"name":"Product"}}}' \
  "https://app.514.ax/api/v1/context/mutations?org_id=$AX_ORG_ID"

Actions are read, options, preview-delete, mutate, mutate-many, flow-steps, and document upload actions. Objects use create, update, and delete; relationships use attach and detach. models, agent-versions, user-flow-steps, and user-flow-step-capabilities are read-only through this editor. Updates require the current expectedUpdatedAt; deletion requires the token returned by preview-delete.

Deleting a root (companies, products, use-cases, personas, agents) archives it rather than removing it: preview-delete returns archives: true with no effects and is always allowed, and after the delete the object leaves every list, picker, embedded relationship, and count on this API, the CLI, MCP, and the platform; it no longer counts as tag usage, and a new owned record, link, tag assignment, or experiment association that names it is refused as not found. The object itself stays readable at its own id: GET /context/{kind}/{id} and its /documents return it with archived_at and archived_by set, the platform shows its page marked as archived and read-only, and its existing owned content, links, and experiment associations are kept, so experiments that referenced it keep working. Deleting an owned record or link still removes it, and preview-delete still reports what else that touches.

POST /api/v1/context/{kind}/{id}/copy

Copy a global companies, products, use-cases, personas, or agents root and its related Context into the selected organization. The response echoes the kind you sent.

curl -X POST \
  -H "Authorization: Bearer $AX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"request_id":"<UUID>"}' \
  "https://app.514.ax/api/v1/context/products/<CONTEXT_UUID>/copy?org_id=$AX_ORG_ID"

Reuse request_id only to retry the same copy.

The copy carries the published tags of the root and every object copied with it. Each shared tag is reused from the organization's library (matched first by the shared tag it was copied from, then by name) or created there with the shared name and color, and the copied objects receive the same assignments. Locally renamed or recolored tags keep their edits, and local tags and assignments are never removed. When a shared tag's name would collide with a different organization tag, the whole copy fails with a failed_precondition error naming both tags; rename or delete one of them and send the request again.

POST /api/v1/context/tags

Manage tags, the reusable labels members attach to Context objects. Send one command per request. Organization tags and their assignments are yours to edit; the shared library's tags are read-only here (they are administered by Fiveonefour, and shared assignments arrive through suggestions). Every result is JSON; the ManageContextTags Connect method wraps the same result in {result: ...}.

curl -X POST \
  -H "Authorization: Bearer $AX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"create","name":"Launch ready","color":"#0ea5e9"}' \
  "https://app.514.ax/api/v1/context/tags?org_id=$AX_ORG_ID"

scope defaults to org; global reads the shared library and is refused with 403 on create, update, delete, assign, and unassign. kind is an object type from targets, such as companies or products. Names are unique per organization ignoring case and surrounding spaces, up to 64 characters. color is #rrggbb or a palette name, and null clears it. limit defaults to 50 and accepts 1 through 100. includeUsage adds a usageCount to each tag.

The commands are safe to retry:

• create returns the existing tag with created: false when the name is already taken, so a retried create never duplicates a tag.
• assign and unassign return created: false or removed: false when the assignment was already in the requested state.
• update requires the tag's current updatedAt as expectedUpdatedAt and returns 409 when the tag changed since you read it.
• delete removes the tag from every object. Once a tag is in use, send the count from usage as expectedUsageCount; a mismatch returns 412 with the current count so you can confirm again. The count is in the message and in details as [{"type":"axp.v1.ContextTagUsageChanged","value":{"usageCount":N}}], so a client can read it without parsing text.

# Attach a tag to a Company, then list the Companies carrying it.
curl -X POST -H "Authorization: Bearer $AX_API_KEY" -H "Content-Type: application/json" \
  -d '{"action":"assign","kind":"companies","targetId":"<CONTEXT_UUID>","tagId":"<TAG_UUID>"}' \
  "https://app.514.ax/api/v1/context/tags?org_id=$AX_ORG_ID"
curl -H "Authorization: Bearer $AX_API_KEY" \
  "https://app.514.ax/api/v1/context/companies?org_id=$AX_ORG_ID&filter.tags=<TAG_UUID>"

GET /api/v1/context/tags runs the read actions from query parameters: action (targets, list, get, usage, or assigned; default list) plus scope, search, after, limit, kind, tagId, targetId, and includeUsage. Reuse next_page_token only with the same organization, scope, tag, and kind filter.

Invalid input returns 400; an unknown tag or object returns 404; another organization's tag, or a shared-library write, returns 403.

POST /api/v1/context/claims

Read a claim status, submit or verify publisher evidence, issue a DNS challenge, or withdraw a claim. Claims accept companies, products, agents, personas, use-cases, and documents for status. Ownership-changing actions are limited to companies, products, and agents and require an organization admin.

curl -X POST \
  -H "Authorization: Bearer $AX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"status","kind":"products","id":"<CONTEXT_UUID>"}' \
  "https://app.514.ax/api/v1/context/claims?org_id=$AX_ORG_ID"

Context follows

GET /api/v1/context/follows, POST /api/v1/context/follows, and DELETE /api/v1/context/follows read, start, and stop your own follow of a companies, products, use-cases, personas, or agents object. Follows belong to the authenticated person, persist across organization switches, and never list other followers.

scope selects which object the id names. global (the default) is a shared catalog object, which you follow by opting in. org is an object owned by an organization you belong to; every member follows the organization's objects by default, so DELETE opts you out of that object's activity and POST opts you back in. With scope=org, org_id names the owning organization and is required when your key belongs to several; with the global scope it is optional and only selects the organization whose feature rollout applies.

curl -H "Authorization: Bearer $AX_API_KEY" \
  "https://app.514.ax/api/v1/context/follows?kind=products&id=<CONTEXT_UUID>"

curl -X POST \
  -H "Authorization: Bearer $AX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"kind":"products","id":"<CONTEXT_UUID>"}' \
  "https://app.514.ax/api/v1/context/follows"

# Stop following one of your organization's own products.
curl -X DELETE \
  -H "Authorization: Bearer $AX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"kind":"products","id":"<ORG_CONTEXT_UUID>","scope":"org"}' \
  "https://app.514.ax/api/v1/context/follows?org_id=<ORG_ID>"

GET takes kind, id, and scope as query parameters; POST and DELETE take them in the JSON body, with org_id staying in the query string. Each response is {following: boolean}.

POST /api/v1/context/suggestions

Send one suggestion workflow action.

curl -X POST \
  -H "Authorization: Bearer $AX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"list","pendingOnly":true}' \
  "https://app.514.ax/api/v1/context/suggestions?org_id=$AX_ORG_ID"

proposed may contain only editable fields for the target kind. evidence is an array of up to five {url, description} values. idempotencyKey is a UUID; reuse it when retrying the same submission. To replace a pending suggestion, send both replacesRequestId and expectedVersion.

A tag suggestion proposes 1 to 40 changes across add and remove, with no tag in both; every id must exist in the shared library, and you can hold one pending tag suggestion per shared object. Staff review it and publish the result; shared objects never take direct assign calls. A 422 response means the proposal can no longer be published (for example a proposed tag was deleted); withdraw it or submit a replacement.

If the shared record changed after the snapshot, refresh it and submit a new proposal. A 409 response means the submitted version conflicts with the current review state. Invalid input returns 400; an unavailable target or feature returns 404; request limits return 429. The JSON request body is limited to 128 KiB; oversized bodies return 413.