Skip to main content

Official Python SDK for Axme APIs.

Project description

axme-sdk-python

Official Python SDK for the AXME platform. Send and manage intents, observe lifecycle events, work with inbox and approvals, and access the full enterprise admin surface — all from idiomatic Python.

Alpha · API surface is stabilizing. Not recommended for production workloads yet.
Alpha access: https://cloud.axme.ai/alpha · Contact and suggestions: hello@axme.ai


What Is AXME?

AXME is a coordination infrastructure for durable execution of long-running intents across distributed systems.

It provides a model for executing intents — requests that may take minutes, hours, or longer to complete — across services, agents, and human participants.

AXP — the Intent Protocol

At the core of AXME is AXP (Intent Protocol) — an open protocol that defines contracts and lifecycle rules for intent processing.

AXP can be implemented independently.
The open part of the platform includes:

  • the protocol specification and schemas
  • SDKs and CLI for integration
  • conformance tests
  • implementation and integration documentation

AXME Cloud

AXME Cloud is the managed service that runs AXP in production together with The Registry (identity and routing).

It removes operational complexity by providing:

  • reliable intent delivery and retries
  • lifecycle management for long-running operations
  • handling of timeouts, waits, reminders, and escalation
  • observability of intent status and execution history

State and events can be accessed through:

  • API and SDKs
  • event streams and webhooks
  • the cloud console

What You Can Do With This SDK

The AXME Python SDK gives you a fully typed client for the AXME platform. You can:

  • Send intents — create typed, durable actions that the platform guarantees to deliver
  • Observe lifecycle — stream real-time state transitions, waiting events, and delivery confirmations
  • Approve or reject — handle human-in-the-loop steps directly from Python code
  • Control workflows — pause, resume, cancel, update retry policies and reminders mid-flight
  • Administer — manage organizations, workspaces, service accounts, and access grants

Install

pip install axme

Primary import path is axme (legacy axme_sdk remains as compatibility alias).

For local development from source:

python -m pip install -e ".[dev]"

Quickstart

from axme import AxmeClient, AxmeClientConfig

client = AxmeClient(
    AxmeClientConfig(
        api_key="AXME_API_KEY",  # sent as x-api-key
        actor_token="OPTIONAL_USER_OR_SESSION_TOKEN",  # sent as Authorization: Bearer
        # Optional override (defaults to https://api.cloud.axme.ai):
        # base_url="https://staging-api.cloud.axme.ai",
    )
)

# Check connectivity
print(client.health())

# Send an intent to a registered agent address
intent = client.create_intent(
    {
        "intent_type": "order.fulfillment.v1",
        "to_agent": "agent://acme-corp/production/fulfillment-service",
        "payload": {"order_id": "ord_123", "priority": "high"},
    },
    idempotency_key="fulfill-ord-123-001",
    correlation_id="corr-ord-123-001",
)
print(intent["intent_id"], intent["status"])

# List registered agent addresses in your workspace
agents = client.list_agents(org_id="acme-corp-uuid", workspace_id="prod-ws-uuid")
for agent in agents["agents"]:
    print(agent["address"], agent["status"])

# Wait for resolution
resolved = client.wait_for(intent["intent_id"])
print(resolved["status"])

Minimal Language-Native Example

Short basic submit/get example (about 25 lines):

Run:

export AXME_API_KEY="axme_sa_..."
python examples/basic_submit.py

Full runnable scenario set lives in:


API Method Families

The SDK covers the full public API surface organized into families. The map below shows all method groups and how they relate to the platform's intent lifecycle.

API Method Family Map

Each family corresponds to a segment of the lifecycle or an operational domain. Intents and inbox are D1 (core). Approvals, schemas, and media are D2. Enterprise admin and service accounts are D3.


Create and Control Sequence

From calling create_intent() to receiving a delivery confirmation — the full interaction sequence with the platform:

Create and Control Sequence

The SDK sets the Idempotency-Key and X-Correlation-Id headers automatically. The gateway validates, persists, and returns the intent in PENDING state. The scheduler picks it up and drives delivery.


Idempotency and Replay Protection

Every mutating call in the SDK accepts an optional idempotency_key. Use it for all operations you might retry.

Idempotency and Replay Protection

Duplicate requests with the same key return the original response without re-executing. Keys expire after 24 hours. The SDK will warn if you reuse a key with different parameters.

# Safe to call multiple times — only executes once
intent = client.create_intent(payload, idempotency_key="my-unique-key-001")

Observing Intent Events

The SDK provides a streaming event observer that delivers real-time lifecycle events over SSE:

for event in client.observe(intent["intent_id"]):
    print(event["event_type"], event["status"])
    if event["status"] in {"RESOLVED", "CANCELLED", "EXPIRED"}:
        break

Approvals and Human-in-the-Loop

# Fetch pending approvals for an agent
pending = client.list_inbox(owner_agent="agent://manager")

for item in pending.get("items", []):
    thread_id = item.get("thread_id")
    if not thread_id:
        continue
    # Approve the inbox thread with a note
    client.approve_inbox_thread(
        thread_id,
        {"note": "LGTM"},
        owner_agent="agent://manager",
    )

Workflow Controls

Update retry policy, reminders, or TTL on a live intent without cancelling it:

client.update_intent_controls(
    intent_id,
    {
        "controls": {
            "max_retries": 5,
            "retry_delay_seconds": 30,
            "reminders": [{"offset_seconds": 3600, "note": "1h reminder"}],
        }
    },
    policy_generation=intent["policy_generation"],
)

SDK Diagrams

The SDK docs folder contains diagrams for the API patterns used by this client:

Diagram Description
01-api-method-family-map Full API family overview
02-create-and-control-sequence Intent creation and control flow
03-idempotency-and-replay-protection Idempotency protocol

MCP (Model Context Protocol)

The Python SDK includes a built-in MCP endpoint client for gateway-hosted MCP sessions:

# Initialize an MCP session
init = client.mcp_initialize()
print(init["serverInfo"])

# List available tools
tools = client.mcp_list_tools()
for tool in tools.get("tools", []):
    print(tool["name"])

# Call a tool
result = client.mcp_call_tool("create_intent", arguments={
    "intent_type": "order.fulfillment.v1",
    "payload": {"order_id": "ord_123"},
    "owner_agent": "agent://fulfillment-service",
})
print(result)

MCP calls go to /mcp by default. Override with mcp_endpoint_path in AxmeClientConfig.


Tests

pytest

Repository Structure

axme-sdk-python/
├── axme/
│   ├── client.py              # Canonical public import path
│   └── exceptions.py          # Canonical exception import path
├── axme_sdk/
│   ├── client.py              # AxmeClient — all API methods
│   ├── config.py              # AxmeClientConfig
│   └── exceptions.py          # AxmeAPIError and subclasses
├── tests/                     # Unit and integration tests
├── examples/
│   └── basic_submit.py        # Minimal language-native quickstart
└── docs/

Related Repositories

Repository Role
axme-docs Full API reference and integration guides
axme-spec Schema contracts this SDK implements
axme-conformance Conformance suite that validates this SDK
axme-examples Runnable examples using this SDK
axme-sdk-typescript TypeScript equivalent
axme-sdk-go Go equivalent

Contributing & Contact

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

axme-0.1.2.tar.gz (26.9 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

axme-0.1.2-py3-none-any.whl (16.3 kB view details)

Uploaded Python 3

File details

Details for the file axme-0.1.2.tar.gz.

File metadata

  • Download URL: axme-0.1.2.tar.gz
  • Upload date:
  • Size: 26.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for axme-0.1.2.tar.gz
Algorithm Hash digest
SHA256 62310ec48b6cbad28e1b337fa83a76f5e1fe5107d7c3d34f3265b687b300a9ef
MD5 a1d3cabfe9c0aacf78961d6a39a0e753
BLAKE2b-256 ad28173715b80d64e0c05725e6a57db01487cb7ae3bf663a92ad3ff7588444c6

See more details on using hashes here.

File details

Details for the file axme-0.1.2-py3-none-any.whl.

File metadata

  • Download URL: axme-0.1.2-py3-none-any.whl
  • Upload date:
  • Size: 16.3 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for axme-0.1.2-py3-none-any.whl
Algorithm Hash digest
SHA256 8c43b745785a8608f8e747fd8d674d62a4a8cf640fcc4f911fb050af89ac79de
MD5 da411e4f3cd4f72fe2f5ab5a73daba07
BLAKE2b-256 df143b34d3ec1aa5b1c05151b7b5e4889aa7439eba099c56316d2d7d6c96a88c

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page