This release is a pre-release and may not be stable for production use.
stigmer
Python SDK for the Stigmer platform. Provides typed API clients for all Stigmer resources with authentication, error handling, and cross-resource search.
Installation
pip install stigmer-sdk
stigmer-apis (generated protobuf stubs) is installed automatically as a dependency.
Quick Start
from stigmer import StigmerClient, AgentInput
with StigmerClient("sk_live_abc123") as client:
agent = client.agents.create(AgentInput(name="my-agent", org="my-org"))
print(agent.metadata.name)
Or without a context manager:
client = StigmerClient("sk_live_abc123")
agent = client.agents.get("agent-id")
client.close()
Resource Clients
Every resource type has a typed client accessible as a property on StigmerClient:
| Property | Resource |
|---|---|
agents |
Agent |
runs |
Run |
api_keys |
ApiKey |
grants |
Grant |
identity_accounts |
IdentityAccount |
federation_issuers |
FederationIssuer |
organizations |
Organization |
plugins |
Plugin |
sessions |
Session |
skills |
Skill |
vaults |
Vault |
search |
Cross-resource search |
tokens |
User-token minting (service-account keys) |
Common Operations
from ai.stigmer.agentic.agent.v1 import io_pb2 as agent_io_pb2
from ai.stigmer.commons.apiresource import io_pb2 as apiresource_io_pb2
from stigmer import StigmerClient, AgentInput, ResourceRef
with StigmerClient("sk_live_abc123") as client:
# Create
agent = client.agents.create(AgentInput(
name="my-agent",
org="my-org",
description="Handles customer inquiries",
instructions="Be helpful and concise.",
))
# Get by ID
agent = client.agents.get("agent-id")
# Get by reference (org + slug)
agent = client.agents.get_by_reference(ResourceRef(org="my-org", slug="my-agent"))
# Update: read, change, then name the fields you changed. Every other
# field keeps its stored value. The read's etag makes the save fail with
# "aborted" if someone changed the agent since.
current = client.agents.get("agent-id")
current.spec.description = "Updated description"
updated = client.agents.update(current, ["spec.description"])
# Rename: change the slug people type. The id stays, so everything that
# points at the agent keeps working; the old slug reads for 30 days.
renamed = client.agents.rename(
apiresource_io_pb2.RenameInput(resource_id="agent-id", slug="support-bot")
)
# Delete
deleted = client.agents.delete("agent-id")
# List: one page of the org's agents, newest first. A page carries
# next_page_token while more follow; page_size 0 asks for the default 50.
page = client.agents.list(agent_io_pb2.ListAgentsRequest(org="my-org", page_size=20))
# Every agent, page after page: list_all follows the tokens.
for a in client.agents.list_all(agent_io_pb2.ListAgentsRequest(org="my-org")):
print(a.metadata.slug)
# Only the agents carrying every label given.
support = client.agents.list(
agent_io_pb2.ListAgentsRequest(org="my-org", labels={"team": "support"})
)
Cross-Resource Search
from stigmer import StigmerClient, ApiResourceKind, SearchParams
with StigmerClient("sk_live_abc123") as client:
results = client.search.query(SearchParams(
kinds=[ApiResourceKind.agent, ApiResourceKind.skill],
org="my-org",
query="customer support",
))
User Tokens
A product that embeds Stigmer mints a short-lived token for each person
signed in to it, from its own backend, with an ordinary client built on a
service account's API key. The account must be an admin of the organization
the token is for, or of its parent organization; a person's key is refused.
Pass access_token to the React SDK's StigmerProvider through
getAccessToken:
from stigmer import StigmerClient
with StigmerClient(os.environ["STIGMER_API_KEY"]) as client:
result = client.tokens.mint_user_token(
org="acme",
user_id=user.id,
user_email=user.email,
user_name=user.name,
)
print(result.access_token, result.expires_at)
Billing
An organization's billing account (its Stripe customer), the Stripe portal
and card setup sessions. Token usage is read from the run client's usage
reports (get_run_usage_report, get_session_usage_report,
get_agent_usage_report, get_org_usage_report), counted in tokens and never
priced. Queries require can_view_billing on the org and the org's own
billing commands require can_manage_billing. The operator pricing methods
(list_model_pricing_baselines, upsert_model_pricing_baseline,
retire_model_pricing_baseline) require can_manage_model_pricing on the
platform:
from stigmer import CreatePaymentMethodSetupSessionParams, StigmerClient
with StigmerClient("sk_live_abc123") as client:
account = client.billing.get_billing_account(org)
setup = client.billing.create_payment_method_setup_session(
CreatePaymentMethodSetupSessionParams(
org=org,
success_url="https://example.com/billing?setup=success",
cancel_url="https://example.com/billing",
)
)
Error Handling
All SDK operations raise StigmerError with structured error codes:
from stigmer import StigmerClient, StigmerError, is_not_found, is_retryable
with StigmerClient("sk_live_abc123") as client:
try:
agent = client.agents.get("nonexistent")
except StigmerError as err:
if is_not_found(err):
print("Agent not found")
elif is_retryable(err):
print("Transient error, retry later")
else:
print(f"Error [{err.code.value}]: {err}")
Error codes: not-found, permission-denied, unauthenticated, invalid-argument, already-exists, resource-exhausted, failed-precondition, internal, unavailable, cancelled, unknown.
Configuration
StigmerClient(
api_key: str, # Stigmer API key (required)
*,
base_url: str = "api.stigmer.ai:443", # gRPC target address
insecure: bool = False, # Skip TLS (local development only)
)
For a CI job or a script, use a service account's API key, not a person's: it keeps working when that person leaves and works only in its own organization.
Code Generation
The resource clients in src/stigmer/_gen/ are generated from protobuf service schemas. To regenerate after proto changes:
cd sdk/python
make codegen
Handwritten code lives in src/stigmer/ (outside _gen/): _client.py, _transport.py, _interceptors.py, _search.py, _tokens.py, and __init__.py.
Metadata
Release files for stigmer-sdk 0.1.0.dev0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| stigmer_sdk-0.1.0.dev0.tar.gz | 46.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| stigmer_sdk-0.1.0.dev0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 113.3 kB
Release files / stigmer_sdk-0.1.0.dev0.tar.gz
| Download URL | stigmer_sdk-0.1.0.dev0.tar.gz |
|---|---|
| Size | 46.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e393693047e7fba23bf3e5f19441894d30a00b0f8d2bf84c573b65b31584d079
|
|
BLAKE2b-256 checksum How to use checksums |
61986e4988c5f06f68ddb4407edf86ecd4be4790e7bb36684db847fff18a0a73
|
| 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 17, 2026.
Transparency logRelease files / stigmer_sdk-0.1.0.dev0-py3-none-any.whl
| Download URL | stigmer_sdk-0.1.0.dev0-py3-none-any.whl |
|---|---|
| Size | 66.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
844a1783e5db9255ff220d1f882f48287beab624077eaf8dd0dc800946bd8d46
|
|
BLAKE2b-256 checksum How to use checksums |
e98d995184c856c7ec9faab515e73927997fe03a7e3c4c550693cfb4cb4a37c4
|
| 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 17, 2026.
Transparency log