Skip to main content

singularity-grid

Python SDK for the SGL Network confidential compute grid. Submit inference jobs to TEE-verified nodes, check grid capacity, and use the OpenAI-compatible chat completions endpoint -- all from a single package.

Installation

pip install singularity-grid

To use the OpenAI compatibility helper:

pip install singularity-grid[openai]

Quick start

1. OpenAI-compatible usage (simplest)

The SGL Network orchestrator exposes an OpenAI-compatible /v1/chat/completions endpoint. You can use the standard openai package with no wrapper:

from openai import OpenAI

client = OpenAI(
    base_url="https://grid.x402compute.cc/v1",
    api_key="scg_your_api_key",
)

response = client.chat.completions.create(
    model="gemma-4-26b",
    messages=[{"role": "user", "content": "Hello"}],
)
print(response.choices[0].message.content)

2. Helper function

If you prefer not to copy the URL, use the built-in helper:

from singularity_grid import create_openai_client

client = create_openai_client(api_key="scg_your_api_key")

response = client.chat.completions.create(
    model="gemma-4-26b",
    messages=[{"role": "user", "content": "Hello"}],
)
print(response.choices[0].message.content)

3. GridClient (full grid features)

For grid-specific features like job submission, TEE attestation, capacity checks, and pricing:

from singularity_grid import GridClient

# Public endpoints -- no auth required
grid = GridClient()
capacity = grid.capacity()
models = grid.models()
pricing = grid.pricing()

print(f"Active nodes: {capacity.active_nodes}/{capacity.total_nodes}")
for m in models:
    print(f"  {m.id} -- {m.sgl_node_count} nodes")

# Authenticated endpoints
grid = GridClient(api_key="scg_your_api_key")

job = grid.submit_job(
    model="gemma-4-26b",
    input_payload={
        "messages": [{"role": "user", "content": "Analyze this data"}]
    },
    submitter_wallet="0xYourWallet",
    submitter_chain="base",
)

print(f"Job {job.job_id}: {job.status}")

# Retrieve result and attestation
result = grid.get_job(job.job_id)
attestation = grid.get_attestation(job.job_id)
print(f"TEE verified: {attestation.verified}")

API reference

GridClient

Method Auth Description
capacity() No Grid-wide capacity summary
models() No Available models with pricing and TEE info
pricing() No Pricing table for all models
submit_job(model, input_payload, ...) Yes Submit a compute job
get_job(job_id) Yes Get job status and result
get_attestation(job_id) Yes Get TEE attestation proof

Exceptions

Exception When
SGLError Base class for all SDK errors
SGLAPIError Non-2xx response from the API
SGLAuthError 401 or 403 response
SGLNotFoundError 404 response
SGLConnectionError Orchestrator unreachable or timeout

Configuration

Parameter Default Description
api_key None Bearer token for authenticated endpoints
base_url orchestrator URL Override the orchestrator URL
timeout 60.0 Request timeout in seconds

License

MIT

Processors

Processors are served by processors.x402compute.cc, not the grid, so they have their own client.

from singularity_grid import ProcessorsClient

p = ProcessorsClient(api_key=os.environ["SGL_API_KEY"])

p.catalogue()                          # public, no credential
p.list()                               # yours          (processors:read)
p.deploy(manifest, code)               # returns the invoke token ONCE
p.update("my-processor", code=code)
p.set_listing("my-processor", True)
p.run("my-processor", {"name": "world"}, invoke_token)

processors:write is full control of processors owned by that key's wallet — delete and secrets included, the same as a Cloudflare API token. Mint processors:read if you want a credential that cannot change anything. Note that compute keys do not expire, there is no audit log, and delete is permanent: the code is wiped and the slug is burned forever.

run() takes the invoke token from deploy(), not the API key — the run route is the only one with both a money path and an anonymous buyer lane, so it does not read a key as an ownership claim. Buyers use run_with_payment() with an x402 header instead.

Upgrading from 0.8.x

The six processor methods on GridClient (deploy_processor, invoke_processor, list_processors, get_processor, delete_processor, get_processor_logs) are removed, along with the Processor* models. They pointed at /grid/processors, which has never existed — every call returned 404 — and their models described an older design that was never shipped. Use ProcessorsClient. Nothing else changed: chat, embeddings, jobs, models, capacity, pricing, reserve and the vault are untouched.

Release files for singularity-grid 0.9.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 singularity-grid 0.9.0
File Size Uploaded
singularity_grid-0.9.0.tar.gz 24.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for singularity-grid 0.9.0
File Interpreter ABI Platform
singularity_grid-0.9.0-py3-none-any.whl Python 3 none any Details

Total release size: 49.8 kB

Release files / singularity_grid-0.9.0.tar.gz

Download URL singularity_grid-0.9.0.tar.gz
Size 24.4 kB
Tags Source
SHA-256 checksum
How to use checksums
0f9c8f993e1b2a334d90589eddbe6d49f5e80d798d697aa3de3c87a15a27233e
BLAKE2b-256 checksum
How to use checksums
dcb15ecf5c9283ab8e101599c7dd02b68b139c045fb43661bef7479de219326d
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 Sep 8, 2026.

Transparency log

Release files / singularity_grid-0.9.0-py3-none-any.whl

Download URL singularity_grid-0.9.0-py3-none-any.whl
Size 25.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3bb28a1f87b766a28c535f59e80ea0a262bca32a7f4373bc3e5676802e52f6f9
BLAKE2b-256 checksum
How to use checksums
66c4ee1d55e418fa4c54e380342a5935a58144cb9f491b662abbe2b55c1da5e6
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 Sep 8, 2026.

Transparency log

Release history Release notifications | RSS feed

0.9.1

2 release files

This release

0.9.0 This release

2 release files

0.8.0

2 release files

0.7.0

2 release files

0.6.0

2 release files

0.5.0

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.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