Api
Call the Auron API on the user's behalf. Use whenever the user asks to look up, create, update, or delete anything in Auron — agents, meetings, conversations, entities, signals, knowledge stores, teams, telephony, analytics, etc. Also use when an Auron-related question is best answered by hitting a live endpoint. Authenticates by calling the Auron MCP server's exchange_token tool and caching the bearer token in ~/.auron/config.json.From its SKILL.md
npx -y skills add oraczen/auron-claude-plugin --skill apiAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
6.0 KB, as published. Nobody here has run it
Auron API
A bundled CLI (auron-api) lets you discover, search, and call any endpoint in the Auron OpenAPI spec. Authentication is handled via the Auron MCP server — no browser flow, no client secret.
Flow:
- Auth. If
~/.auron/config.jsonis missing, call the MCP toolmcp__claude_ai_auron__exchange_tokento get a bearer token, then pipe it intoauron-api set-tokento cache it. - Sync the spec into
~/.auron/openapi.jsonand a per-tag wiki at~/.auron/api-wiki/<tag>.md(only when missing or stale). - Search for the endpoint relevant to the user's request.
- Load only the wiki file(s) you need into context.
- Call the endpoint — the CLI uses the cached token automatically.
Host info
- Wiki present: !
test -d ~/.auron/api-wiki && echo yes || echo no - Token present: !
test -f ~/.auron/config.json && echo yes || echo no - OS / arch: !
uname -s/ !uname -m
Pick the right binary
Use the host symlink on Unix: ${CLAUDE_SKILL_DIR}/bin/auron-api. On Windows pick auron-api-windows-amd64.exe. Full matrix:
| OS / arch | Binary |
|---|---|
| macOS arm64 | auron-api-darwin-arm64 |
| macOS amd64 | auron-api-darwin-amd64 |
| Linux amd64 | auron-api-linux-amd64 |
| Linux arm64 | auron-api-linux-arm64 |
| Windows amd64 | auron-api-windows-amd64.exe |
Step 1 — Ensure auth
The Auron MCP server is configured at the project level (.mcp.json). It handles user authentication; you just need to fetch the bearer token it issues for the connected user.
If ~/.auron/config.json does not exist (or an API call returns 401):
-
Call the MCP tool
mcp__claude_ai_auron__exchange_token(no arguments). It returns the OAuth2 bearer token as a plain string. -
Pipe the returned token into the CLI to cache it:
printf '%s' "<token-from-mcp>" | "${CLAUDE_SKILL_DIR}/bin/auron-api" set-tokenThis writes
{"access_token": "..."}to~/.auron/config.jsonwith0600perms. The token is cached indefinitely — only re-run this if a call later returns 401.
Never echo the token to the user, and never write it anywhere other than via set-token.
Step 2 — Ensure the spec is synced
If ~/.auron/api-wiki/ is missing or older than 24h, run:
"${CLAUDE_SKILL_DIR}/bin/auron-api" sync
This writes ~/.auron/openapi.json plus one markdown file per tag.
Step 3 — Find the right endpoint
Run search against the user's intent — do not load wiki files blindly.
"${CLAUDE_SKILL_DIR}/bin/auron-api" search "schedule meeting with rep" --limit 10
Returns JSON with method, path, operationId, summary, tags, and the wiki filename. Pick the most plausible match. If unsure, search again with different terms or list sections:
"${CLAUDE_SKILL_DIR}/bin/auron-api" list
Step 4 — Load only the wiki you need
Read the specific ~/.auron/api-wiki/<tag>.md file with the Read tool. Don't read every file — pick 1–3 based on search results. Each tag file lists every operation with parameters, request-body shape, and response codes. For the full schema of a request/response body, read the relevant components.schemas block from ~/.auron/openapi.json.
Step 5 — Call the endpoint
"${CLAUDE_SKILL_DIR}/bin/auron-api" call GET /agents --query "limit=20"
"${CLAUDE_SKILL_DIR}/bin/auron-api" call POST /meetings --body @/tmp/payload.json
echo '{"title":"Discovery call"}' | "${CLAUDE_SKILL_DIR}/bin/auron-api" call POST /meetings --body -
Flags:
| Flag | Form | Notes |
|---|---|---|
--query | --query "k=v,k2=v2" | Comma-separated key=value pairs |
--header | --header "X-Trace=abc" | Extra request headers |
--body | --body @file.json or - | File path (prefixed @) or stdin (-) or literal |
--raw | --raw | Print response body verbatim (skip JSON pretty-print) |
The CLI:
- Reads the
Bearertoken from~/.auron/config.json. - Resolves the base URL from
servers[0].urlin the synced openapi (currentlyhttps://dev.useauron.ai/api/v1), so thepathyou pass starts at/. - Pretty-prints JSON to stdout, writes
METHOD URL → statusto stderr. - Exits non-zero on HTTP ≥ 400.
Rules
- Auth is a prerequisite. If
~/.auron/config.jsonis missing, run the MCP exchange +set-tokensteps above. If a call returns 401, the cached token is stale — repeat the exchange to refresh it. - Read params before calling. Always check the wiki entry's parameter list before constructing a call; mandatory path/query params produce 4xx otherwise.
- Mutations require confirmation. Before any
POST,PUT,PATCH, orDELETE, summarize what will happen (method, path, body) and ask the user to confirm. Reads are safe to run unprompted. - Don't echo tokens or full response bodies that may contain PII. Summarize, and offer to show specific fields.
- Don't loop. If a call returns 4xx, read the error, fix the request, and try once more — then stop and ask the user.
- Don't invent endpoints. Only call paths that appear in
searchresults or the wiki.