GET
/api/agents/entitiesbearer tokenRead and write the agent’s graph
Everything an agent gathers lands in one elastic graph of typed nodes. Dashboard pages are views over it. This is the same data, directly: read a kind, create a node, update it, delete it.
Try it
curl "https://storkie.ai/api/agents/entities?id=YOUR_AGENT_ID&kind=task" \
-H "Authorization: Bearer YOUR_TOKEN"No Run button: this needs your bearer token, and a docs page that asks for one is teaching people to paste credentials into web forms.
Query parameters
| Name | Type | Description |
|---|---|---|
idrequired | string | The agent ID. |
kind | string | Filter to one node kind (`task`, `event`, `person`…). |
nodeId | string | One node, for PATCH and DELETE. |
title / props / status | various | Body fields when creating or updating. |
Response
| Name | Type | Description |
|---|---|---|
nodes | array | Matching nodes with their props and edges. |
counts | object | How many of each kind exist. |
Worth knowing
- The graph is backed by Firestore or Postgres depending on deployment. The API is identical either way — that is the whole point of the abstraction.
Rate limit
60 requests / minute / account
Errors
401— Missing or invalid token.404— Not yours, or no such agent or node.
Questions
Do I have to define a schema first?
No. Kinds and props are open; the agent creates what the conversation needs.
How does this relate to dashboard pages?
A page is a view over this data. The catalog at /pages lists every way it can be rendered.