Skip to content
Anlyon
Esc
↑↓navigate↵open⌘Jpreview
On this page

Anlyon API

Anlyon is the production execution runtime for AI agents. An agent invokes a named action; Anlyon resolves the action and its version, checks the caller’s scopes, evaluates policy, requests human approval when required, resolves credentials at dispatch, makes the production call itself, and records the outcome.

These guarantees cover actions routed through the hosted executor. A tool the caller’s own code invokes directly, with a credential that process holds, is not routed through Anlyon and is not governed by it.

Authentication

Developer API endpoints use a workspace API key as a bearer token:

Authorization: Bearer anlyon_your_api_key

API-key budget admission

Budgets reserve supported logical operations in Postgres with integer sub-cent cost accounting. They cover messages, event publishes, cache lookups, memory operations and action invocations; external provider bills and session callers are outside these caps. UTC calendar months own the reservations. Batches reserve all planned items before execution; partial failures retain that amount. Memory ingest reserves one job admission, not each generated chunk or token. Approval-pending actions reserve one invocation admission even before dispatch. These conservative admission estimates are distinct from invoice metering.

429 BUDGET_EXCEEDED refuses the whole admission. 503 BUDGET_RECONCILIATION_REQUIRED pauses keys whose legacy usage is unknown. A cached Idempotency-Key success replays normally. If that cache is lost or expires but a durable budget reservation exists, 409 BUDGET_EFFECT_ALREADY_RESERVED prevents executing the effect again. Investigate the original outcome before choosing a new key; a new key can duplicate work. Errors after admission keep their reservations until an operator proves no work occurred. Disabling or deleting a budget does not erase recorded usage.

Delivery signature environment attribution

Configured message and event-subscription signers emit legacy v1 plus signed env/v2 attribution. v2 is HMAC-SHA256 over the exact UTF-8 string anlyon-delivery-v2.${timestamp}.${environmentId}.${rawBody}. Receivers must configure the expected environment independently; v1 alone provides no environment boundary. Signing keys remain workspace-wide unless a subscription uses its own secret. X-Anlyon-Environment-Id is reserved and informational, not authority. Legacy queued work without recorded scope has no v2 claim. See /verification for coverage, raw-body verification and staged migration.

Rate Limiting

Rate limits are based on your workspace plan:

  • Free Plan: 300 requests/minute, 10,000 requests/hour
  • Pay as You Go: Unlimited
  • Enterprise: Custom limits

Error Handling

All errors follow a consistent format:

{
  "success": false,
  "error": {
    "code": "ERROR_CODE",
    "message": "Human-readable error message",
    "details": {}
  }
}

Common error codes:

  • AUTHENTICATION_ERROR - Invalid or missing API key
  • RATE_LIMIT_EXCEEDED - Too many requests
  • QUOTA_EXCEEDED - Usage quota exceeded
  • VALIDATION_ERROR - Invalid request data
  • NOT_FOUND - Resource not found
  • FEATURE_NOT_AVAILABLE - Feature not available on your plan
Version 2.0.0
Base URLhttps://api.anlyon.comhttp://localhost:4000

Messages

Publish and manage scheduled messages

Schedules

Create and manage recurring schedules (cron jobs)

URL Groups

Manage URL groups for broadcasting messages

Analytics

View analytics and usage statistics

Billing

Manage billing, plans, and usage

Notifications

Manage notifications and preferences

Sessions

Persist agent conversation threads and prompt-ready history

Context

Assemble memory and session state into prompt-ready context

Actions

Define and invoke secret-backed hosted tools

Impact Limits

Shared business-impact limits (money, resource mutations) that governed effects reserve before dispatch. Separate from Budgets, which cap Anlyon usage.

Approval Policies

Configure the environment-scoped rules that decide whether a request needs approval, is auto-approved, or is auto-denied. Operator credentials only.

Authentication

Inspect the credential making the request

Approvals

Create and decide human-in-the-loop safety gates

Budgets

Control per-API-key usage and estimated spend

Secrets

Store write-only credentials used by hosted actions

Files

Upload, inspect, download, and delete workspace files

Cache

Store and semantically retrieve reusable model results

Events

Publish typed events and deliver them to filtered webhook subscriptions

DLQ

Inspect, retry, and permanently remove exhausted message deliveries

Flow Control

Coordinate per-key rate limits, parallelism, pausing, and delivery waitlists

Integrations

Connect Slack and Discord notification destinations without exposing stored credentials

Logs

Query, inspect, and export redacted message and schedule execution history

Queues

Configure isolated message streams with parallelism, pause/resume controls, and live lag

Workflows

Define callback-driven workflows, trigger runs, inspect steps, and resume event waits

Memory

Stream

Runs

Environments

Was this page helpful?