Skip to main content

A2SPA Python Payload Helpers

Helper-only Python package for building, hashing, and signing A2SPA runtime authorization payloads.

The verifier remains server-side. This package does not authorize actions by itself.

Install

pip install a2spa

For ML-DSA signing support where the optional wheel is available:

pip install "a2spa[pq]"

Basic Usage

from pathlib import Path

from a2spa import build_payload_fields, build_signed_request, policy_input

private_key_text = Path("sender.priv.pem").read_text(encoding="utf-8")

payload = build_payload_fields(
    agent_id="user-123_sender",
    target_agent_id="user-123_receiver",
    input_data=policy_input(action="deliver", workflow_scope="messages:deliver"),
)

request_body = build_signed_request(private_key_text, payload)

Send request_body to POST /api/verify_payload with your account API key in the x-api-key header.

Helper Functions

  • build_payload_fields(...)
  • policy_input(...)
  • policy_template(...)
  • state_continuity_claim(...)
  • canonicalize_payload(...)
  • compute_payload_hash(...)
  • finalize_payload(...)
  • sign_payload(...)
  • build_signed_request(...)
  • is_authorized_result(...)
  • require_authorized_result(...)
  • verify_execution_receipt(...)
  • enforce_target_authorization(...)
  • build_target_acknowledgement(...)
  • execute_protected_action(...)
  • build_debug_snapshot(...)

Signed Bytes

Current helper compatibility signs the UTF-8 bytes of json.dumps(signable_payload, sort_keys=True) using the normalized signable fields. Do not reimplement canonicalization unless your bytes match canonicalize_payload(...) exactly.

Security Boundary

Private keys must stay in a secret manager, server environment, or deployment secret. Do not paste private keys into chats, logs, client-side code, or source control.

A2SPA 2.1 Target Enforcement

A2SPA 2.1 adds a deployment profile for protected targets. The target, trusted gateway, service, or executor should fail closed unless the A2SPA authorization result is valid for the exact operation being committed.

from a2spa import build_target_acknowledgement, enforce_target_authorization

authorization = enforce_target_authorization(
    result,
    target_agent_id="user-123_email-target",
    action="send_email",
    workflow_scope="email:send",
    trusted_receipt_public_key_pem=trusted_a2spa_receipt_public_key,
)

# Commit the protected side effect only after enforce_target_authorization returns.
provider_result = email_provider.send(message)

target_ack = build_target_acknowledgement(
    authorization,
    target_id="smtp-gateway",
    operation_id=message["idempotency_key"],
    result={"provider_message_id": provider_result.id},
)

If the agent can reach another route that commits the same protected consequence without this guard, the deployment fails the A2SPA 2.1 profile.

Metadata

Release files for a2spa 0.1.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for a2spa 0.1.4
File Size Uploaded Provenance
a2spa-0.1.4.tar.gz 11.5 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for a2spa 0.1.4
File Interpreter ABI Platform
a2spa-0.1.4-py3-none-any.whl Python 3 none any Details

Total release size: 20.3 kB

Release files / a2spa-0.1.4.tar.gz

Download URL a2spa-0.1.4.tar.gz
Size 11.5 kB
Tags Source
SHA-256 checksum
How to use checksums
b56c3df3c723dd42428b944015854ff6e57d3aceb5be9405ccf85df0504e973a
BLAKE2b-256 checksum
How to use checksums
4f1014e40b929dfdcfadb4f4a876a08ea6d08c5f69b9df642ca17eb7216ff5f6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.9

Release files / a2spa-0.1.4-py3-none-any.whl

Download URL a2spa-0.1.4-py3-none-any.whl
Size 8.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
39e7ae46824ab4bc2d2f8d11f6435b56c26fdb7ccce8b3baed9e2391e744a834
BLAKE2b-256 checksum
How to use checksums
3695cee6b66f9a3e44dc253c4a0173c6233baf2887d96e2f033d64cac5b82aaa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.9

Security for a2spa 0.1.4

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page