signalcore
SignalCore's server SDK for Python: your backend makes organizations for your customers, sets up
their agents, talks to them and hears what happens, through SignalCore's public API
(https://signalcore.ai/v1). Every operation of the API is a typed method; the SDK holds no logic
of its own.
pip install "signalcore>=2" # uv add, poetry add alike
Python 3.10 or later. Version 2 is for SignalCore 2.0's API; 0.x was for the API it replaced.
Quickstart
Make a secret key (sk_…) in SignalCore, keep it on your server, and talk to an agent:
from signalcore import SignalCore
client = SignalCore("sk_…") # or set SIGNALCORE_API_KEY
squad = client.squads.list()[0]
agent = client.agents.create(squad["id"], name="Recepción", instructions="Answer briefly.")
conversation = client.conversations.start(agent["id"])
reply = client.conversations.say(conversation["id"], text="¿Abrís el sábado?", wait=True)
print(reply["status"], reply["replies"][0]["text"])
With wait=True the answer comes when the agent's turn ends (up to a minute): status is done,
waiting (on a question or an approval, in waiting) or failed (error). Without it the call
answers at once with running, and the reply comes on the live socket or a webhook.
Answers are plain dicts typed with TypedDicts (signalcore.types), so your editor knows every
field.
Your customers' organizations
A key acts on its own organization, or on one it manages with org:
customer = client.orgs.create(name="Clínica Norte")
theirs = SignalCore("sk_…", org=customer["id"]) # SignalCore-Org
theirs.squads.list() # their own agents, data and channels, never shared
A person in your page
Your backend mints a token for the person (an hour, the agents it names), and your page talks with
it (@signalcore/ui):
token = client.tokens.create(agents=[agent["id"]], external_id=user.id, name=user.name)
return {"token": token["token"]}
Live
Every frame of a conversation as it happens (message, text, step, done, …), as an async
iterator:
from signalcore import AsyncSignalCore
async with AsyncSignalCore("sk_…") as client:
async with client.conversations.live(conversation_id) as live:
await live.say("Hola")
async for frame in live:
if frame["type"] == "done":
break
SignalCore has the same live(), iterated with a plain for. AsyncSignalCore has every
method of SignalCore, awaited.
Webhooks
Register an endpoint (client.webhooks.create(url=…, events=[…]) answers its secret once), and
check each delivery before trusting it, with the body exactly as it came:
from signalcore import SignatureError, verify
@app.post("/signalcore")
async def hook(request: Request):
try:
event = verify(await request.body(), request.headers, WEBHOOK_SECRET)
except SignatureError:
raise HTTPException(400)
if event["type"] == "message.created":
...
client.webhooks.verify is the same function.
Errors
Whatever the API refuses or fails raises one ApiError: status (HTTP), code to decide by
(not_found, forbidden, busy, rate_limited, …) and detail, a sentence you can show.
from signalcore import ApiError
try:
client.agents.get("agt_…")
except ApiError as error:
if error.code == "not_found":
...
Every operation
Each operation of the API reference is a method named from its id, <group>_<verb>: agents_get
is client.agents.get(agent_id), agents_memories_create is client.agents.memories_create(…).
A few read better renamed: conversations.say (conversations_messages_create), runs.list and
runs.get, agents.create(squad_id, …); signalcore.OPERATIONS maps every id to its method.
- Path parameters are positional; the body's fields and the query are keyword arguments.
- A field left out isn't sent;
Nonesendsnull. - Writes take
idempotency_key=: the same key answers the first answer again for a day. - Lists read page after page with
iter:for run in client.runs.iter(agent=agent_id): …(activity.itertoo). - Files go up as bytes (
client.files.put("catalog.pdf", data, content_type="application/pdf")) and come down as bytes (client.files.get("catalog.pdf")).
Developing it
Half of the package is generated from the API's contract (v3/api/openapi.json):
_resources.py and _types.py, by python v3/clients/generate.py. The rest is by hand:
_base.py (requests, errors, pages), _extras.py (the live socket, webhooks). When the contract
changes, generate again; CI fails while they differ.
uv sync
uv run pytest # against the local API (v3-api) at http://localhost:8300, or SIGNALCORE_TEST_API
uv run mypy && uv run ruff check
The tests that need an API sign up an owner of their own there and skip themselves when none answers.
Metadata
Release files for signalcore 2.0.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 | |
|---|---|---|---|---|
| signalcore-2.0.0.tar.gz | 101.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| signalcore-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 139.4 kB
Release files / signalcore-2.0.0.tar.gz
| Download URL | signalcore-2.0.0.tar.gz |
|---|---|
| Size | 101.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7771a4da27e40076dc43906b5cbfffb89c23c563b406ef7786281524843b788
|
|
BLAKE2b-256 checksum How to use checksums |
d64defa2da68e104a07f0707dfb6442556f470370f681b1ac38607c48ff3e17c
|
| 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 20, 2026.
Transparency logRelease files / signalcore-2.0.0-py3-none-any.whl
| Download URL | signalcore-2.0.0-py3-none-any.whl |
|---|---|
| Size | 38.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0cdb00d69059b0b7d6f57250d1da2763f1695f421a2f1963ede8ba6f658f435e
|
|
BLAKE2b-256 checksum How to use checksums |
e2cca9bbb436b208659668bfd46cfe92070e8604a789337177b01cc81fa3f624
|
| 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 20, 2026.
Transparency logSecurity for signalcore 2.0.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for signalcore-2.0.0.tar.gz
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 20, 2026.
Transparency logA 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.