Developer Tools

pauli.xyz

Provides access to quantum computing devices for circuit execution and estimation.

1 endpoint17 known toolsFirst detected July 16, 2026Last detected August 23, 2026

ENDPOINT 1

https://pauli.xyz/mcp

No auth detected

MCP server metadata

Name: pauli
Version: 0.6.2

Capabilities

tools

Server instructions

Pauli routes OpenQASM 3 circuits across quantum hardware providers and returns canonical counts (bit_ordering cbit0_left: leftmost character is classical bit 0). Recommended loop: list_devices to see the fleet; estimate_job to price a circuit on every eligible device; dry_run_job to validate the exact submit body for free (returns the routing decision, the exact wallet debit, an admission preview, and complete per-device exclusion reasons); submit_job (set idempotency_key so retries are safe); then job_status until terminal and job_results for counts. get_balance and list_wallet_entries show the prepaid wallet and what each job debited. A 402 billing.insufficient_credits tool error is fundable: its error.detail.payment names the rail; create_topup starts a hosted checkout for a human to complete, list_payments or get_balance confirm crediting, then resubmit with the same idempotency_key. The spend-cap 402s (billing.monthly_cap_exceeded, billing.key_cap_exceeded) carry no payment challenge: report them to your operator instead of paying. Every error carries a stable machine-readable code (list_error_codes serves the full registry); on a tool error, read error.code and error.detail and repair the request. Authenticate by sending your API key as an 'Authorization: Bearer <key>' header on this endpoint.

Known tools 17

list_devices

The live device registry: provider, qubits, capabilities, queue depth, status, and price model per device.

Inferred read-only

get_device

One device's registry entry by id.

Inferred read-only

estimate_job

Price a circuit on every eligible device without enqueueing: per-device cost, what the wallet would debit, predicted queue seconds, fidelity score, plus reasoned exclusions for the rest.

Inferred read-only

dry_run_job

The full submit preview, free: runs the identical validate/route path as submit_job and returns the routing decision a real submit would carry, the exact wallet debit, a read-only admission preview (would_admit, blocked_by), and the COMPLETE per-device exclusion reasons with stable machine codes.

Inferred read-only

submit_job

Submit a circuit for execution.

Inferred read-only

job_status

Job state, state history, device, and (once billed) the exact price.

Inferred read-only

job_results

Canonical measurement counts (bit_ordering cbit0_left) with register map, provenance metadata, and billing.

Inferred read-only

cancel_job

Request cancellation.

Inferred read-only

list_jobs

This workspace's jobs, newest first (order=asc for oldest first).

Inferred read-only

related_jobs

Workspace jobs sharing a circuit fingerprint with the given job, bucketed by relation kind — repetition, device_comparison, parameter_sweep, observable_battery, angle_variants — with a newest-first member preview and, per bucket, the exact list_jobs/group_insights filter for the whole family.

Inferred read-only

group_insights

Cross-job analytics over every job the filters match (a sweep's members, an experiment's metadata pair, explicit ids): exact spend/state/device roll-ups at any size, plus — within the analysis cap — pooled-histogram insights, repetition consistency with calibration-drift attribution, sweep series with extrema and sinusoid fits, optimizer-trace convergence (best point, plateaued, spend-to-best), device bake-off tables, and assembled observable batteries.

Inferred read-only

get_balance

The prepaid wallet: balance, reserved (estimated debits held by in-flight jobs), and available (balance minus reserved, what admission checks).

Inferred read-only

list_wallet_entries

The wallet journal, newest first: top_up, debit (per job, with job_id), refund, adjustment, and dispute entries with exact decimal USD amounts.

Potential side effects

create_topup

Start a hosted-checkout wallet top-up (admin key).

Inferred read-only

list_payments

Top-up payment history, newest first: status (pending, succeeded, failed, cancelled, disputed), exact USD amount, checkout_url while a hosted checkout is still pending, and the receipt link once credited.

Potential side effects

list_error_codes

The full stable error-code registry (code, HTTP status, summary).

Inferred read-only

device_benchmarks

Published benchmark runs from Pauli's landscape data product (scores, instances, receipts) filtered by device or definition.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.pauli]
url = "https://pauli.xyz/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "pauli": {
      "type": "http",
      "url": "https://pauli.xyz/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: pauli
Remote MCP URL: https://pauli.xyz/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "pauli": {
      "url": "https://pauli.xyz/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "pauli": {
      "type": "http",
      "url": "https://pauli.xyz/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "pauli",
  "transport": "streamable-http",
  "url": "https://pauli.xyz/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for pauli.xyz was fetched 2026-09-06T17:14:20.025Z.

Trust status New

This domain appears to have previously been parked, so its current status is new or unverified.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.