Server details
The API key goes on the connection, never in a tool argument, so it stays out of the LLM’s context. Each connection speaks for the system that owns the key.
Connect your agent
- Claude Code
- Cursor
- n8n
Available tools
emit_delta
Reports one event to Aether.
Returns the Delta’s
id and received_at. If the payload does not match the event’s contract, the tool returns an error telling the agent what to fix, so it can retry.
trigger_plan
Asks Aether which systems should run.
Returns the Trigger Plan. Only the environment’s top-level orchestrator can call it.
Example prompts
When a Connected System is an AI agent, its system prompt tells it when and how to call the Aether tools. Adapt these examples to your agents.- Agent: emit_delta
- Orchestrator: trigger_plan
An agent that reports what it did after finishing its work. Here, a newsroom writer.
Always include the system’s System Contract in the prompt of an agent that calls
emit_delta. It lists the events the system may report and the schema of each payload, so the AI knows which event to send and how to build payload. Without it, the AI may invent events or send payloads that do not match the contract. Invented events are not rejected: they are added to the contract. Copy it from the system’s contract in the Aether Dashboard, with View JSON.Troubleshooting
trigger_plan returns a permission error
trigger_plan returns a permission error
Only the top-level orchestrator can request a plan. Connect with the orchestrator system’s API key.
emit_delta says the payload must be a JSON-encoded object string
emit_delta says the payload must be a JSON-encoded object string
payload is a string, not an object. Encode the object as JSON first, e.g. "{\"status\": \"ok\"}".Payload rejected
Payload rejected
The payload does not match the event’s contract. Fix the fields named in the error and retry.

