Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/usewrit-app:usewrit-app-secrets-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Writ Agent Secrets API
version: 0.1.0
license:
name: MIT
identifier: MIT
description: 'Loopback HTTP API of the Writ local agent (`writ-agentd`), the daemon embedded in the
Writ desktop app and the self-host build. This document is generated against the Rust
daemon source (`writ-agent/src/local/`), which is the wire truth.
## Transport
- Plain HTTP on `127.0.0.1:8131` (default; `WRIT_PORT` env overrides).
- Optional HTTPS twin on `127.0.0.1:8132`, served with a certificate minted by a
per-install, name-constrained local CA (`~/.writ/tls/ca.pem`). Clients must trust that
CA file (or pin it) to use the TLS port; the payloads are identical on both ports.
- The daemon enforces a DNS-rebind guard: `Host`/`Origin` must be loopback. Talk to
`127.0.0.1`, not `localhost`.
## Errors
Domain errors are JSON `{"error": "", "code": ""}` (see the
`Error` schema). Codes include `bad_request`, `unauthorized`, `forbidden`, `not_found`,
`vault_locked` (HTTP 423), `too_many_requests`, `device_capacity` (HTTP 409),
`captcha_required` (HTTP 402), `internal`.
**Caveat:** some 4xx bodies are `text/plain`, not JSON — axum framework rejections
(e.g. a JSON body that fails to deserialize returns
`Failed to deserialize the JSON body into the target type: missing field ''url''` as
plain text with a 4xx status). Clients must tolerate non-JSON error bodies.
## List envelopes
The wire is deliberately documented as-is (SDKs normalize; this spec does not):
- `{"data": [...], "count": n}` — workflows, personas, persona runs, secrets, files, keys
- `{"data": [...], "count": n, "total": n}` — runs
- **bare JSON array** — monitors, monitor selectors, extractors, automations,
`/v1/changes/recent`
- bespoke objects — `/v1/monitors/{id}/changes`, `/v1/data`, the workflow-data table'
servers:
- url: http://127.0.0.1:8131
description: Plain-HTTP loopback listener (default port; WRIT_PORT overrides).
- url: https://127.0.0.1:8132
description: HTTPS twin of the same API, terminated with a certificate from the per-install local CA at ~/.writ/tls/ca.pem. Trust that CA (or pin it) in your HTTP client.
security:
- bearerAuth: []
tags:
- name: Secrets
description: Vault secrets addressed by unique text key; values never leave the daemon.
paths:
/v1/secrets:
get:
operationId: listSecrets
tags:
- Secrets
summary: List secrets (metadata only)
description: Newest-first secret metadata in the `{data, count}` envelope. Ciphertext and plaintext values are never included. Returns 423 while the vault app-lock is locked.
parameters:
- name: limit
in: query
description: Page size (clamped to 1..=500; default 100).
schema:
type: integer
format: int64
default: 100
- name: search
in: query
description: Case-insensitive substring match on the secret name.
schema:
type: string
- name: category
in: query
description: Restrict to a single category (e.g. `credentials`, `card`, `api_keys`).
schema:
type: string
responses:
'200':
description: Secret metadata page in the `{data, count}` envelope.
content:
application/json:
schema:
$ref: '#/components/schemas/SecretList'
'401':
$ref: '#/components/responses/Unauthorized'
'423':
$ref: '#/components/responses/VaultLocked'
post:
operationId: createSecret
tags:
- Secrets
summary: Create a secret
description: Creates a single-value secret (`value`), a credential pair (`username` + `password`), or a card (`card` object with at least `number` and `expiry`). The plaintext is sealed handler-side; the response is metadata only. A duplicate name is a 400. Returns 423 while the vault app-lock is locked.
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/SecretCreate'
responses:
'200':
description: The created secret's metadata.
content:
application/json:
schema:
$ref: '#/components/schemas/Secret'
'400':
$ref: '#/components/responses/BadRequest'
'401':
$ref: '#/components/responses/Unauthorized'
'423':
$ref: '#/components/responses/VaultLocked'
/v1/secrets/{key}:
parameters:
- $ref: '#/components/parameters/SecretKey'
get:
operationId: getSecret
tags:
- Secrets
summary: Get one secret's metadata
description: Metadata ONLY — the value is never returned over the API. Returns 423 while the vault app-lock is locked.
responses:
'200':
description: The secret's metadata.
content:
application/json:
schema:
$ref: '#/components/schemas/Secret'
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
'423':
$ref: '#/components/responses/VaultLocked'
delete:
operationId: deleteSecret
tags:
- Secrets
summary: Delete a secret
description: Hard-delete by key. Returns 423 while the vault app-lock is locked.
responses:
'200':
description: Deletion acknowledgement.
content:
application/json:
schema:
type: object
required:
- key
- deleted
properties:
key:
type: string
deleted:
type: boolean
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
'423':
$ref: '#/components/responses/VaultLocked'
components:
schemas:
Error:
type: object
description: 'The daemon''s domain error body. NOTE: some 4xx responses (axum framework rejections) are `text/plain` instead of this JSON shape. Certain codes attach extra fields (e.g. `device_capacity` adds `would_use_units_per_min` / `budget_units_per_min`; `captcha_required` adds `captcha_type` / `url`).'
required:
- error
- code
properties:
error:
type: string
description: 'Human-readable message (e.g. `not found: workflow 999999`).'
code:
type: string
description: 'Stable machine code: `bad_request`, `unauthorized`, `forbidden`, `not_found`, `vault_locked`, `too_many_requests`, `captcha_required`, `device_capacity`, `cloud_unreachable`, `db_error`, `io_error`, `json_error`, `internal`, …'
additionalProperties: true
Secret:
type: object
description: Secret METADATA (the value/ciphertext is never returned). `name` mirrors `key` (cloud parity). Credential secrets surface their non-secret `username`; card secrets surface only `card_last4`.
required:
- id
- key
- name
- description
- category
- is_credential
- is_card
- username
- card_last4
- created_at
- updated_at
- last_used_at
- use_count
properties:
id:
type: integer
format: int64
key:
type: string
name:
type: string
description: Alias of `key`.
description:
type:
- string
- 'null'
category:
type:
- string
- 'null'
description: e.g. `credentials`, `card`, `api_keys`.
is_credential:
type: boolean
description: True only for a real `{username, password}` pair.
is_card:
type: boolean
username:
type:
- string
- 'null'
description: The credential pair's username (never the password).
card_last4:
type:
- string
- 'null'
description: Last 4 digits of a card secret's number (never the full PAN/CVC).
created_at:
type: string
updated_at:
type:
- string
- 'null'
last_used_at:
type:
- string
- 'null'
use_count:
type:
- integer
- 'null'
format: int64
SecretCreate:
type: object
description: 'Create body — exactly one of three shapes: a single `value`, a credential pair (`username` + `password`), or a `card` object (needs at least `number` and `expiry`). `key` is a legacy alias for `name`. Name pattern: `^[a-zA-Z_][a-zA-Z0-9_.-]*$`, max 255 chars. Plaintext is sealed handler-side.'
properties:
name:
type:
- string
- 'null'
description: The unique secret name (required unless `key` is given).
key:
type:
- string
- 'null'
description: Legacy alias for `name`.
value:
type:
- string
- 'null'
description: Single-value secret plaintext.
username:
type:
- string
- 'null'
description: Credential-pair username (with `password`).
password:
type:
- string
- 'null'
description: Credential-pair password (with `username`).
card:
type:
- object
- 'null'
description: 'Card fields: `{name, number, expiry, cvc, zip}` (strings).'
properties:
name:
type: string
number:
type: string
expiry:
type: string
cvc:
type: string
zip:
type: string
description:
type:
- string
- 'null'
category:
type:
- string
- 'null'
SecretList:
type: object
description: '`{data, count}` list envelope.'
required:
- data
- count
properties:
data:
type: array
items:
$ref: '#/components/schemas/Secret'
count:
type: integer
responses:
NotFound:
description: The addressed resource does not exist.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
VaultLocked:
description: The vault app-lock is engaged and locked (HTTP 423). Unlock via `POST /v1/vault/unlock`.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
Unauthorized:
description: Missing/invalid bearer token, or the Origin/Host guard rejected the request.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
BadRequest:
description: 'Invalid input. Domain validation errors use the JSON Error shape; axum body-deserialize rejections are `text/plain` with a bare message (e.g. `Failed to deserialize the JSON body into the target type: missing field ''url''`).'
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
text/plain:
schema:
type: string
parameters:
SecretKey:
name: key
in: path
required: true
description: The secret's unique text key (its name).
schema:
type: string
securitySchemes:
bearerAuth:
type: http
scheme: bearer
description: "Every route (including `/v1/agent` and `/v1/health`) requires\n`Authorization: Bearer <token>`. Token families:\n\n- `wlt_…` — the runtime token from `runtime.json` (full access, used by the desktop\n UI and SDK discovery).\n- `wlk_…` — a scoped API key minted via `POST /v1/keys` (CSV scopes `read|run|admin`;\n `/v1/keys` itself requires the full-access token).\n- `wlo_…` — an OAuth 2.1 access token from the daemon's local authorization server\n (`run` scope).\n\nTreat the token as an opaque string. The daemon additionally enforces a loopback\nOrigin/Host DNS-rebind guard.\n"