Automation API

Transports and framing

bluep api uses one compact JSON-RPC request per input line. HTTP uses POST /api/rpc.

Run bluep api --model model-directory; responses are written only for requests with an id.

Team viewers may read and editors may apply changes. Authentication happens before RPC dispatch.

Requests use JSON-RPC 2.0 with jsonrpc, id, method, and object params.

An omitted id executes without a response.

Protocol errors use the standard -32700 through -32603 range; model state errors use -32001 onward.

All paths are confined beneath the configured root.

rpc.discover returns supported methods and whether each mutates a model.

Open the configured model with { "dir": "." }.

Returns validation issues.

Lists stable object keys by kind.

Fetches one object by selector.

Applies Phase 42 editor actions with a base fingerprint.

Generates DDL, diagrams, or documentation.

Compares an open model with a current source.

Plans a target migration.

Runs lint with a minimum severity.

Returns impact analysis for a selector or comparison.

Renders a built-in report family.

Binary report data uses padded RFC 4648 base64.

New methods are additive; existing response fields retain their meaning.