Simple, predictable pricing
for code execution

Yes. Basic costs $0 per month and includes 500 requests per RapidAPI subscription period. It is designed for evaluation, prototypes, and small workloads.

One call to any endpoint counts as one RapidAPI request. A batch call is one request regardless of the number of items; each session endpoint call is a separate request. Batch plan limits are maximum accepted item counts, not parallelism guarantees: items run through bounded workers and the entire batch request has a 150-second wall-clock budget. Starting an async job is one request, and each later polling call is another request.

RapidAPI measures bandwidth in 1 MB units, with 10,240 MB/month currently included on every plan, then charges $0.001 per MB above that allowance. This platform fee is separate from the subscription-period request allowance and the proxy's per-execution transfer safety cap. Check RapidAPI for current billing settings.

Paid session installs publish only the artifacts you explicitly request. pip accepts cached wheels only with --only-binary=:all: --no-deps --no-build-isolation; source distributions are rejected. npm downloads with npm pack --ignore-scripts, validates and extracts the direct package, and strips dependency and lifecycle-script metadata. List every required package explicitly; transitive dependency resolution is planned. The deprecated options.no_deps field is forced true, so setting it to false does not enable dependencies.

RapidAPI applies and resets the request allowance on its subscription period, along with any marketplace overage settings shown for your selected plan. SandboxAPI separately applies only the per-minute burst limit and returns rate-limit headers so clients can throttle proactively.

Plan changes are managed in your RapidAPI account and follow the marketplace terms shown when you subscribe or change plans.

Yes, for paid API plans with explicit opt-in on single, streaming, or async execution and on session creation. Network stays off by default, and Basic plus the browser playground cannot enable it. Pro can request managed public HTTPS but cannot submit custom domain rules. Ultra and Mega may optionally provide up to 32 exact domains or explicit *.example.com rules; an empty list means all public HTTPS. Batch execution stays networkless and rejects network.enabled=true so one outbound budget maps to one RapidAPI request. Customer-facing audit logs and a static egress IP remain planned or deployment-dependent.

The proxy accepts HTTPS CONNECT only on port 443, resolves public IPv4 destinations, rejects raw-IP and private, internal, or special-purpose destinations, pins DNS, requires matching outer TLS SNI, and uses signed short-lived per-execution tokens. This is explicit proxy-based egress, not transparent networking: your client must honor HTTPS_PROXY or be configured for it. Some Node built-in fetch and Java configurations do not do that automatically, and raw public sockets are unavailable. Production defaults cap each execution at 8 concurrent tunnels and 25 MiB aggregate transfer, with duration capped by the execution timeout. It relays opaque TLS rather than inspecting HTTP content, so domain rules are routing controls—not content-level DLP. Connection outcomes are recorded in structured operator egress logs. A session's destination policy is fixed at creation, current plan eligibility is rechecked, and credentials refresh on every execute. Stable pip/npm installs use a separate managed install-proxy path only after firewall/topology and mirror/OSV readiness checks pass; otherwise installs are disabled.

Self-hosting is not currently supported. If you have a regulated-environment or on-premises requirement, contact hello@sandboxapi.dev.

RapidAPI handles self-serve billing, invoices, cancellations, plan changes, and refunds under its marketplace terms.