Skip to main content

Rymi Python SDK

The official Python wrapper for the Rymi Voice AI API — build and run AI voice agents from any Python app.

Manage agents (including multi-language and full model-stack control), phone numbers, calls, knowledge sources, evaluations, usage, and templates — plus webhook verification.

PyPI version Python versions PyPI downloads license

Documentation · API Reference · Dashboard · Node SDK · MCP Server


✨ Why Rymi

🎙️ Voice agents Full STT → LLM → TTS stack control, per-channel fallbacks, and multi-language support.
☎️ Telephony Register numbers, place outbound calls, and observe them live.
📚 Knowledge Ground agents in your own docs and data with managed knowledge sources.
📊 Usage & evals Track minutes and spend, then run evaluations to keep quality high.
🔒 Secure by default Built-in webhook signature verification; keys read from the environment.

📦 Installation

pip install rymi

Requires Python 3.8+.

🚀 Quick Start

import os
from rymi import Rymi

# Automatically picks up RYMI_API_KEY from the environment
client = Rymi()

# Or pass it explicitly
# client = Rymi(api_key="rymi_live_...")

agents = client.agents.list()
for agent in agents["agents"]:
    print(agent["name"])

Tip: Keep your secret key in RYMI_API_KEY and let the client read it — never hard-code secret keys.

🧩 Resources

The client exposes one namespace per resource group:

Namespace What it does
agents Create, update, clone, and configure voice agents
calls Place, list, and observe calls; fetch transcripts and recordings
numbers Register and attach phone numbers
telephony Inspect carrier status and provisioned numbers
keys Manage publishable keys
billing Usage summaries and balance
templates Prebuilt agent templates
webhooks Create webhooks and verify incoming signatures
dnc Do-not-call list management
campaigns Outbound/inbound calling campaigns: members, launch/pause, reports, improvement suggestions, inbound routes, and the lead-intake URL (campaigns.intake)
contacts Contacts and per-channel consent
compliance Compliance attestations (e.g. an external DNC scrub)
tool_secrets Secrets for API-tool headers, referenced as {{secrets.NAME}}

📖 Documentation

Full reference and guides: docs.rymi.live/api/sdk-python

PyPI: pypi.org/project/rymi

📄 License

MIT © Rymi

Metadata

Release files for rymi 1.4.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 rymi 1.4.0
File Size Uploaded
rymi-1.4.0.tar.gz 18.7 kB Details

Built distribution (wheel)

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

Total release size: 38.4 kB

Release files / rymi-1.4.0.tar.gz

Download URL rymi-1.4.0.tar.gz
Size 18.7 kB
Tags Source
SHA-256 checksum
How to use checksums
7c37ac5c4901ccd1c5c16fe7c796e3ca4dd83d89b8e9df18b2318c2a895295dc
BLAKE2b-256 checksum
How to use checksums
3a246e98920d559bf235d5761c68cdc9e3e80ba2128577a27be78f93a32d4028
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 4, 2026.

Transparency log

Release files / rymi-1.4.0-py3-none-any.whl

Download URL rymi-1.4.0-py3-none-any.whl
Size 19.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5874ffabfe2ce8c5513bd83d6b297f662e5e389abee838227998e7467114050d
BLAKE2b-256 checksum
How to use checksums
a411040190671528d65db9f7a4b1aa0edacfca2682551e3f568ce1c774d2ee51
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 4, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.4.0 This release

2 release files

1.3.0

2 release files

1.2.0

2 release files

1.1.0

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