List agent tools
Returns the agent’s active webhook tools, ordered by position ascending and then by
creation time (oldest first). This is the same order in which the tools are pushed to the
voice provider. Deleted tools are never listed. Credentials (auth_config) are never
returned, but headers are, including any fixed_value you stored in them.
Pagination is offset-based (limit + offset). The response carries no pagination metadata
and no total count: request the next page with offset += limit until a page returns fewer
than limit items. An agent holds at most 50 tools, so the default page is always complete.
Use GET /api/agents/{agentId}/tools/{toolId} for a single tool.
Consistency. Each page is cached per workspace, agent, limit and offset for up to
120 seconds. Writes made through this API invalidate the cache immediately.
Access
- Required scope:
read(orwrite). - Rate limit: General API — 120–600 requests/min per workspace depending on plan. See Rate limits.
- Plan: Available on every plan.
Authentication
Workspace API key: jl_ followed by 64 lowercase hex characters, created by the workspace owner in the
dashboard (Settings → API Keys) and sent as Authorization: Bearer jl_.... The plaintext is shown once,
at creation; Jelliu stores only a SHA-256 hash. A workspace can hold up to 25 active keys.
Operations restricted to admins or owners reject keys without the full scope with 403, and say so in
their description. No key, whatever its scope, can mint or revoke API keys or rotate a webhook secret —
that requires a signed-in owner session. A revoked key stops authenticating within about 10 seconds.
See Authentication.
Path parameters
Query parameters
Maximum number of tools to return, 1–100. Values outside the range or non-integers are rejected with 400 (not clamped).
Number of tools to skip, 0–100000. Values outside the range are rejected with 400.
Response
The page of tools (possibly empty).
Tools ordered by position, then created_at.

