aeo-sdk-python
Python SDK for the AEO Protocol v0.1 — parse, build, validate, and fetch AEO declaration documents.
Install
pip install aeo-protocol
Quickstart
from aeo import Document, fetch_well_known
# Fetch and parse from a live well-known URL
doc = fetch_well_known("https://mizcausevic-dev.github.io")
print(doc.entity.name) # "Miz Causevic"
print(doc.claim_ids()) # ['current-role', 'location', ...]
print(doc.find_claim("years-experience").value) # 30
# Parse from disk
doc = Document.from_file("aeo.json")
# Build programmatically
from aeo import Entity, Authority, Claim, Document
doc = Document(
entity=Entity(
id="https://example.com/#org",
type="Organization",
name="Example Org",
canonical_url="https://example.com/",
),
authority=Authority(primary_sources=["https://example.com/"]),
claims=[Claim(id="tagline", predicate="description", value="A reference example.")],
)
print(doc.to_json())
Async variant:
import asyncio
from aeo.client import fetch_well_known_async
doc = asyncio.run(fetch_well_known_async("https://mizcausevic-dev.github.io"))
What it does
- Parse —
Document.from_json/from_file/from_dict - Build — pydantic v2 model classes for every type in the spec (
Entity,Authority,Claim,Verification,CitationPreferences,AnswerConstraints,Audit) - Serialize —
Document.to_json()returns canonical JSON - Fetch —
fetch_well_known(origin)performs HTTP discovery against/.well-known/aeo.jsonwithAccept: application/aeo+json, application/json - Query —
doc.claim_ids()anddoc.find_claim(id)for convenience
Conformance
This SDK supports the AEO Protocol at conformance Level 1 (Declare). Signature verification (Level 2) and audit-endpoint posting (Level 3) are not yet implemented; signed documents parse fine but the signature is not verified.
Dependencies
Development
pip install -e .[dev]
pytest -v
Specification
Full spec at github.com/mizcausevic-dev/aeo-protocol-spec.
License
MIT-licensed. Free for commercial and non-commercial use with attribution. The AEO Protocol specification this SDK implements is also MIT (see aeo-protocol-spec).
Kinetic Gain Protocol Suite
| Spec | Implementation |
|---|---|
| AEO Protocol | aeo-sdk-python (this) · aeo-sdk-typescript · aeo-sdk-rust · aeo-sdk-go · aeo-cli · aeo-crawler |
| Prompt Provenance | — |
| Agent Cards | — |
| AI Evidence Format | — |
| MCP Tool Cards | — |
Connect: LinkedIn · Kinetic Gain · Medium · Skills
Metadata
Release files for aeo-protocol 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aeo_protocol-0.2.0.tar.gz | 8.7 kB | Without provenance | Details for aeo_protocol-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aeo_protocol-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for aeo_protocol-0.2.0-py3-none-any.whl |
Total release size: 14.7 kB
Release files / aeo_protocol-0.2.0.tar.gz
| Download URL | aeo_protocol-0.2.0.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e284167dff41969b43de03c6a0c4239255f2a553d225986c3adebb11006c668
|
|
BLAKE2b-256 checksum How to use checksums |
bc51d0d053cd85044f7fbc596866a049fa878cadd759e770648ad76a03ff44ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / aeo_protocol-0.2.0-py3-none-any.whl
| Download URL | aeo_protocol-0.2.0-py3-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3528de99612723f5af172b23dffc69f15db168412109b644338953df935b70b1
|
|
BLAKE2b-256 checksum How to use checksums |
efc4af689ff54561386b5b0d9f98f4491a958022adba20c8b8b63364ea148848
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for aeo-protocol 0.2.0
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.