Skip to main content

immersivecommons (Python)

Thin, dependency-free Python client for the Immersive Commons Agent REST API — the surface an AI agent uses to act on Floor 10 of Frontier Tower SF.

The client is derived from the OpenAPI spec: the operations table is generated from a vendored copy of openapi.json, and the transport is table-driven, so the methods cannot drift from the spec.

Install

pip install immersivecommons

Requires Python ≥ 3.9. Zero dependencies (stdlib urllib only).

Quickstart

from immersivecommons import Client

# Public reads need no token:
ic = Client()
events = ic.list_upcoming_events(limit=5)

# Authed calls take an agt_ bearer token:
agent = Client(token="agt_...")
agent.rsvp_to_event(
    "https://luma.com/some-event",
    email="me@example.com",
    idempotency_key="rsvp-2026-07-16-me",  # safe retries
)

Minting a token (device-code flow)

ic = Client()
result = ic.authorize(
    ["events:read_upcoming", "events:rsvp"],
    client_name="my-agent",
    on_prompt=lambda s: print(f"Approve at {s['verify_url']} with code {s['user_code']}"),
)
ic.set_token(result["token"])

Sandbox / test mode

Mint a sandbox token (Client(sandbox=True).authorize(...)) and every WRITE returns a simulated receipt — {"ok": True, "sandbox": True, "simulated": True, "would_have": {...}} — instead of mutating; reads serve real data. A green receipt means well-formed + scoped, not guaranteed to pass every production business rule. Feedback, token revocation, and research reads are always real even with a sandbox token.

Errors

Non-2xx responses raise IcApiError (.status, .error_kind, .retry_after_seconds, .body). It understands both the flat {"error": "..."} shape and the /api catch-all's nested {"error": {"code", "message"}}.

Escape hatch

Every operation is reachable generically:

ic.call("getDonorWall", query={"limit": 10})

The generated OPERATIONS table (path, method, scopes, idempotency, sandbox behaviour) is exported for inspection. The 4 Clerk-cookie-only operations have no methods — agents use the equivalent MCP tools.

Regenerate after a spec bump: python scripts/generate.py.

License

MIT

Metadata

Release files for immersivecommons 0.1.0

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

Source distribution (sdist)

Source distribution for immersivecommons 0.1.0
File Size Uploaded Provenance Actions
immersivecommons-0.1.0.tar.gz 23.3 kB Without provenance Details for immersivecommons-0.1.0.tar.gz

Built distribution (wheel)

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

Total release size: 45.1 kB

Release files / immersivecommons-0.1.0.tar.gz

Download URL immersivecommons-0.1.0.tar.gz
Size 23.3 kB
Tags Source
SHA-256 checksum
How to use checksums
b9299dd9bea5639a3c999d881d066d3afbb033edf1505a3303a6042c920ce47a
BLAKE2b-256 checksum
How to use checksums
7a32a24155e77001809ece805b3eecc6a21f009b2e25019096bebfd94148209d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.12.11

Release files / immersivecommons-0.1.0-py3-none-any.whl

Download URL immersivecommons-0.1.0-py3-none-any.whl
Size 21.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8ed4fd8db55c8e828597f23abb34609fc97f2a312986001ffd059ae42822c729
BLAKE2b-256 checksum
How to use checksums
a13b2fef30b841bfc524ce50a79258e6302e0f75e5f7dc45c518c76d00c90469
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.12.11

Security for immersivecommons 0.1.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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

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