Skip to main content

agience-prism

PyPI Python License CI Sponsor

An environment adapter — prism adapts an environment (world ↔ frame) to Agience. This is the Python adapter: the Agience developer SDK (Apache-2.0).

from prism import Host, create_server

Install

pip install agience-prism

The base install has no dependencies. It carries the contract — canonical JSON, the crystal model, the capability vocabulary, the config shape, the error set, and the structural address — so a component can hold the same answers as every other component without taking on an install cost.

Runtime surfaces are extras:

Extra Installs For
trust python-jose, cryptography the trust floor: keys, signing, scopes
host fastapi, uvicorn, httpx, pyjwt prism.Host
server mcp, httpx prism.create_server
cli cryptography, httpx the prism command line
vector numpy vector types
wire numpy, cryptography the plane: reach, frames, carriers, settlement
all all of the above
dev all + pytest, pytest-asyncio, ruff working on prism itself
pip install "agience-prism[host]"
pip install "agience-prism[all]"

The runtime surfaces resolve through PEP 562 __getattr__, so reaching one without its extra raises an ImportError naming the extra to install, while from prism.canonical import canonical_string costs nothing.

Nine of the sixteen wire modules — carriers, pump, minhash, minting, settlement, extraction, schema, error_threshold, mcp_bridge — import on the bare base install. tests/test_wire_extra.py imports each in a subprocess with numpy and cryptography blocked, so that claim can fail rather than only be asserted.

The aperture is reached by injection (prism.instrument), never by import. A published SDK depends only on packages its consumers can install.

Two toolkits

A host is compute that serves capabilities over HTTP. The platform reaches it over the wire; it imports nothing of the platform.

from prism import Host
from pydantic import BaseModel

host = Host("my-host")


class EchoIn(BaseModel):
    text: str


@host.operator("echo", path="/echo")
def echo(req: EchoIn) -> dict:
    """The function's type hints drive request and response validation."""
    return {"echo": req.text}


app = host.app                  # or: host.serve(port=8083)

api_key=... requires a bearer. A host with no credential configured refuses every operator call; allow_open=True serves them unauthenticated. A JWT is checked against expected_audiences and refused when none is set, unless any_audience=True. host.serve binds 127.0.0.1 unless given another address. EMBER_URI + AGIENCE_TOKEN make the host self-register on start. Routes mounted by hand onto host.app are unauthenticated — use Depends(host.auth_dependency) to apply the same check @host.operator does.

A server exposes MCP tools authorized as the calling user: it captures the inbound delegation token and forwards it on outbound calls, so it only ever acts within that user's authorization.

import json

from prism import create_server

mcp, server = create_server("my-server")


@mcp.tool(description="Echo a message back, with the calling user's id.")
async def echo(message: str) -> str:
    return json.dumps({"echo": message, "user": server.get_user_id()})


app = server.create_app(mcp)    # ASGI; captures the inbound delegation token

The shared contract

prism/vectors/contract_vectors.json is the artifact every prism SDK is checked against — canonical JSON, the crystal sha, the structural address, capability reach. tests/test_contract_vectors.py asserts it here, and each other language leg asserts the same bytes, which is what makes "one wire format, several languages" a measurement.

The vectors ship inside the wheel, so pip install agience-prism is enough to run a conformance gate — no source tree and no sibling checkout:

from prism.vectors import load_vectors
vectors = load_vectors("contract_vectors")

Self-contained

Prism resolves no path outside its own installation and imports nothing from the components that depend on it. Where a deployment supplies data — operator bundles for prism.runner — it names the directory with $AGIENCE_BUNDLE_ROOT or binds a payload with register_group(). Prism never searches for a sibling checkout, because a path derived from where a file happens to sit is a fallback that can drift from the bytes the mesh carries while the integrity gate keeps passing.

Development

pip install -e ".[dev]"
python -m pytest -q
python -m ruff check .

Security issues: email connect@agience.ai rather than opening a public issue.

Licensed under Apache-2.0 — see LICENSE and NOTICE.

Metadata

Release files for agience-prism 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 agience-prism 0.1.4
File Size Uploaded
agience_prism-0.1.4.tar.gz 301.1 kB Details

Built distribution (wheel)

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

Total release size: 543.2 kB

Release files / agience_prism-0.1.4.tar.gz

Download URL agience_prism-0.1.4.tar.gz
Size 301.1 kB
Tags Source
SHA-256 checksum
How to use checksums
16939a5a1db006ae30121e7d2d5eda470a9f65e15b49dd331a6b591a942f3b65
BLAKE2b-256 checksum
How to use checksums
f2ab4921d2f55c22a6f82b933990ff97c178fa12ecc839cbd0a373d283a0c33f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log

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

Download URL agience_prism-0.1.4-py3-none-any.whl
Size 242.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
64eaaeabb862444caab310691093cb685db8fc88081f567e824fe3bd8db5d651
BLAKE2b-256 checksum
How to use checksums
b40c64cac9f171fdae11615a1cccfa93cad12ccc0b9cc64239f1c76a3e1dc449
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.4 This release

2 release files

0.1.2

2 release files

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