Typed clients for agents
Installable TypeScript and Python clients for Orrery's x402 API. They wrap payment challenges, response envelopes, cross-venue endpoints, watchlist summaries, and the Decision API without adding trading or account execution.
@orrery/client
TypeScriptInstall after registry publish
npm install @orrery/client
Agent call
import { OrreryClient, OrreryPaymentRequired } from "@orrery/client";
const orrery = new OrreryClient({
apiKey: process.env.ORRERY_API_KEY,
payment: process.env.ORRERY_X_PAYMENT,
});
try {
const queue = await orrery.attention({ limit: 5 });
console.log(queue.data);
} catch (err) {
if (err instanceof OrreryPaymentRequired) {
console.log(err.challenge);
}
}Source: /sdk/typescript
orrery-client
PythonInstall after registry publish
pip install orrery-client
Agent call
from orrery import OrreryClient, OrreryPaymentRequired
import os
client = OrreryClient(api_key=os.environ.get("ORRERY_API_KEY"))
try:
queue = client.attention(limit=5)
print(queue["data"])
except OrreryPaymentRequired as exc:
print(exc.challenge)Source: /sdk/python
What the SDKs cover
read-onlyThe clients call Orrery only. They do not connect to Kalshi or Polymarket user accounts, submit orders, read positions, or provide trade recommendations.
Local verification
pre-publish# TypeScript cd sdk/typescript npm install npm run build # Python cd sdk/python python -m pip install -e . python -m unittest discover -s tests
Single-file demos
For no-install demos, Orrery still serves dependency-light files from the public site.
Release gate
not published yetThe package code is in-repo and verified locally. Publishing still needs an intentional release command with npm/PyPI credentials. Until then, docs should say package scaffolds are ready rather than claiming packages are available on public registries.