{ "data": { "a": { "slug": "perplexity-space", "name": "SPACE", "vendor": "Perplexity", "vendorUrl": "https://space.docs.perplexity.ai/guide/index.html", "kind": "http-api", "category": "code-sandboxes", "summary": "SPACE is Perplexity's open-source, self-hosted platform for running agent code in Firecracker microVMs. An operator deploys it on Linux with KVM, and applications drive sandboxes through its HTTP and SSE API or an E2B-compatible API.", "url": "https://www.anchorterminal.com/tools/perplexity-space", "markdownUrl": "https://www.anchorterminal.com/tools/perplexity-space.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/perplexity-space.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/perplexity-space.json", "repo": "https://github.com/perplexityai/SPACE", "license": "Apache-2.0", "transports": [ "http" ], "packages": [], "auth": "mixed", "authNotes": "Nothing to sign up for with Perplexity. On a deployment, the native API takes `Authorization: Bearer` with a token from a password login at `/auth/v1/sessions` or a service token, and users hold admin or member roles. Command streams on the data plane take a separate session-scoped token, valid for 5 minutes, that the API returns with each command. The E2B Compatibility Wrapper takes an E2B-style key in `X-API-Key`, which an operator creates with scripts/seed-api-key.sh and an SQL insert. SPACE stores only its SHA-256 hash. No key scopes or revocation call were found in the reviewed documentation.", "pricing": "free", "pricingNotes": "Free under Apache-2.0, with nothing to buy from Perplexity and no hosted SPACE service. The cost is the operator's own hosts, which need Linux x86_64 with KVM (bare-metal instances in Perplexity's reference EKS deployment), plus PostgreSQL and S3-compatible object storage, with Valkey in the reference EKS deployment (checked 2026-10-16).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the README, the docs, the OpenAPI document or the source read on 16 October 2026. Self-hosted open-source software with no paid endpoint.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-16" }, "docsUrl": "https://space.docs.perplexity.ai/guide/index.html", "openapi": "https://space.docs.perplexity.ai/api/openapi.json", "capabilities": [ "sandbox.code", "sandbox.persist", "sandbox.fs" ], "tags": [ "open-source", "self-hosted", "free", "no-card", "apache-2.0", "rust", "linux", "kubernetes", "microvm", "openapi", "e2b-compatible", "pre-1.0", "new" ], "graded": true, "anchor": { "graded": true, "score": 56.2, "grade": "C", "agentReady": false, "rank": 683, "ranked": true, "rankOf": 1098, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 26, "payments": 60, "reliability": 32, "schema": 75, "security": 64, "transparency": 68 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-16" }, "negative": 0, "verdict": "Once deployed, SPACE's native API has a public OpenAPI 3.1 contract, stable error codes with a retryable flag and 24-hour idempotency keys, and egress and credential controls sit outside the VM. A person must first deploy it on a Linux x86_64 host with KVM and Kubernetes. Version 0.8.0 has no tagged release, changelog or public container images.", "bestFor": "Teams that want E2B-style microVM sandboxes on their own Linux and Kubernetes hosts, with egress and credential control outside the guest.", "strengths": [ "OpenAPI 3.1 for 14 supported operations, served by each deployment at `/openapi-m1.json` and published on the docs site", "Errors carry a stable `code`, a `retryable` flag and a request ID, and lifecycle calls and command creation take a 24-hour `Idempotency-Key`", "Per-sandbox egress policies with allow and deny lists, operator egress profiles and TLS interception are enforced by a gateway outside the guest", "The network gateway can add secret headers from AWS Secrets Manager for an exact host and path, so the guest never holds the value", "An E2B Compatibility Wrapper lets the E2B Python SDK, tested at e2b 2.21.1, use a SPACE deployment as its backend" ], "weaknesses": [ "A person must deploy it first, on an apt-based Linux x86_64 host with KVM, privileged Docker and Kubernetes (Kind in the guide)", "Version 0.8.0 has no git tag, GitHub release or changelog, and CI pushes container images only to a private registry", "The `network_policy` and idle-lifecycle create fields are marked incubating, outside the supported contract, and typed as open objects", "Credential injection is off by default, needs AWS Secrets Manager, and has no page of its own in the user guide", "The wrapper rejects E2B's `mcp`, `volumeMounts` and `iam` options, team template names and pause without memory, and only Python is tested" ], "agentNotes": [ "Ask your operator for the API base URL (before `/v1`, or `/api/v1` on shared hosts), the data-plane URL and a bearer token before planning any call", "Poll the returned operation until it succeeds and the sandbox is `running` before creating a command. A 202 response is not readiness", "Attach to the command's events URL with its session token to start the process, decode base64 output, and treat only `process_exited` as completion", "Send an `Idempotency-Key` on creates, lifecycle calls and commands, and retry only when `retryable` is true, after any `Retry-After`", "Save output as it arrives. Reconnecting with `Last-Event-ID` returns `resync_required`, not the missed output" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.2 } ], "editorialScores": { "ergonomics": 66, "maintenance": 26, "payments": 60, "reliability": 32, "schema": 75, "security": 64, "transparency": 73 }, "provenanceScore": 63 }, "connect": { "install": "git clone https://github.com/perplexityai/SPACE.git \u0026\u0026 cd SPACE\nbash infra/space/kind/scripts/install-prereqs.sh\nexport SPACE_VENDOR_ROOT=\"$HOME/.local/share/space/vendor\"\nexport SPACE_KIND_CLUSTER=space-local\nbash infra/space/kind/scripts/install-fc-vendor.sh\nbash infra/space/kind/scripts/bootstrap.sh", "http": "curl --fail-with-body --silent --show-error \\\n --header \"Authorization: Bearer $SPACE_API_TOKEN\" \\\n \"${SPACE_API_URL%/}/v1/sandboxes\"" }, "letme": { "capability": "https://letme.dev/sandbox.code", "tool": "https://letme.dev/perplexity-space" }, "sameCompany": [ "pplx-decider" ], "area": "agent-runtime", "provenance": { "legalEntity": "Perplexity AI", "domain": "perplexity.ai", "domainRegistered": "2022-07-08", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "valid", "checked": "2026-10-16", "notes": [ "LICENSE reads 'Copyright 2026 Perplexity AI', and the repository's Claude Code plugin manifest names Perplexity AI as owner. No fuller legal entity name was found in the repository or the docs.", "The docs site is space.docs.perplexity.ai and the repository is under GitHub's perplexityai organisation. RDAP from Identity Digital gives perplexity.ai a registration date of 8 July 2022.", "No terms or privacy policy applies to the self-hosted software beyond the Apache-2.0 licence. There is no hosted SPACE endpoint, so no status page.", "No changelog or release notes. docs/versioning.md says the v0.8.0 tag should mark the tested commit, and the clone had no tags on 16 October 2026.", "https://www.perplexity.ai/.well-known/security.txt and https://space.docs.perplexity.ai/.well-known/security.txt both returned Contact security@perplexity.ai, Expires 2027-12-31T00:00:00Z and Policy https://www.perplexity.ai/security on 16 October 2026. The robots.txt of www.perplexity.ai allows that path.", "WebFetch refused the docs site as outside its allowed set, so the guide index, API index, openapi.json, build.json files and security.txt were read with curl. space.docs.perplexity.ai has no robots.txt (404). WebFetch refused github.com under its robots.txt, so stars, issues and CI results were not read." ], "score": 63 }, "requirements": { "card": "no", "freeTier": true, "minutes": 120, "credential": "mixed", "hosting": [ "self-hosted" ], "euResidency": "unknown", "trainsOnData": "no", "zeroRetention": "unknown", "selfHost": "yes" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/perplexity-space.json" }, "answer": "SPACE scores 56.2 (C) on agent readiness against Together Code Sandbox's 53.6 (D), and leads in 4 of 7 scored categories. Together Code Sandbox leads on schema \u0026 documentation and maintenance \u0026 community.", "b": { "slug": "together-code-sandbox", "name": "Together Code Sandbox", "vendor": "Together AI", "vendorUrl": "https://www.together.ai", "kind": "http-api", "category": "code-sandboxes", "summary": "Together AI's hosted virtual machine sandboxes for running commands and code, built from Docker-image snapshots and driven from the `together-sandbox` Python SDK, TypeScript SDK or CLI. Access is by allowlist, on request to Together.", "url": "https://www.anchorterminal.com/tools/together-code-sandbox", "markdownUrl": "https://www.anchorterminal.com/tools/together-code-sandbox.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/together-code-sandbox.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/together-code-sandbox.json", "repo": "https://github.com/togethercomputer/together-sandbox", "license": "Proprietary service under Together's terms of service. The SDKs, CLI and OpenAPI documents on GitHub are MIT", "transports": [ "http" ], "remoteUrl": "https://api.bartender.codesandbox.io", "packages": [ { "registry": "pypi", "name": "together-sandbox" }, { "registry": "npm", "name": "together-sandbox" } ], "auth": "api-key", "authNotes": "Access is by allowlist. The docs say the `together-sandbox` SDK and CLI must be enabled for an organisation and to contact Together to request it. Once enabled, a project-scoped Together API key is sent as a Bearer token, read from `TOGETHER_API_KEY`. Keys are revocable, can carry an expiry date and have no finer scopes. Each running sandbox also has its own agent token for the in-VM API, which the SDKs handle.", "pricing": "usage", "pricingNotes": "The pricing page lists Code Sandbox compute at $0.0446 per vCPU-hour and $0.0149 per GiB of RAM per hour, and does not say whether that rate covers the new SDK as well as the legacy one. No free tier or sandbox lets an agent start without a contract. Together has no free trial, platform access needs a $15 first credit purchase, and the organisation must then be enabled on request (https://www.together.ai/pricing, https://docs.together.ai/docs/billing-credits).", "priceSummary": "$0.0446 / vCPU-hr", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs page, the repository or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 3, "npmWeekly": 1298, "pypiWeekly": 3387, "asOf": "2026-10-08" }, "docsUrl": "https://docs.together.ai/docs/together-code-sandbox", "llmsTxt": "https://docs.together.ai/llms.txt", "openapi": "https://togethercomputer.github.io/together-sandbox/api-openapi.json", "capabilities": [ "sandbox.code", "sandbox.fs", "sandbox.persist" ], "tags": [ "hosted", "usage", "allowlist", "sales-led", "openapi", "llms-txt", "python", "typescript", "cli", "security-txt" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 53.6, "grade": "D", "agentReady": false, "rank": 756, "ranked": true, "rankOf": 1098, "categoryRank": 13, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 70, "maintenance": 83, "payments": 20, "reliability": 25, "schema": 86, "security": 47, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Two public OpenAPI documents, MIT clients for Python and TypeScript, cursor pagination and built-in retries make the surface easy for an agent to drive. Access is the limit. Together enables the SDK per organisation on request, publishes no rate limits or SLA, and neither status page names the sandbox service.", "bestFor": "Teams already buying from Together, and former CodeSandbox SDK users, who want Docker-defined sandboxes with disk and memory snapshots from Python or TypeScript.", "strengths": [ "Public OpenAPI documents for the management API (17 operations) and the in-VM API (25), in the repository and on GitHub Pages", "Terminating with `memory: true` saves disk and memory, and a new sandbox created from that snapshot resumes its running processes", "List calls are cursor-paginated (1 to 100 a page) with filters for status, source snapshot and tags", "Both SDKs retry 408, 429 and 5xx three times with exponential backoff, and the docs warn that `snapshots.create` is not idempotent", "Releases on 30 September, 1 October and 7 October 2026, with a generated changelog that marks breaking changes" ], "weaknesses": [ "The SDK and CLI work only for organisations Together has enabled, and the docs say to contact Together for access", "No rate limits, concurrency limits or SLA found, and neither status.together.ai nor status.codesandbox.io names the service", "Every sandbox port is public unless an experimental inbound policy is set, and no outbound controls exist yet", "Three major versions between 2 June and 28 July 2026, and memory snapshots were removed in 4.0.0 and restored in 4.0.4", "The management API answers at `api.bartender.codesandbox.io`, off Together's domain, and the privacy policy's data table has no sandbox row" ], "agentNotes": [ "Confirm the organisation is on Together's allowlist before installing. A valid `TOGETHER_API_KEY` alone is not enough", "Build a snapshot first with `snapshots.create`. No default image exists, and every sandbox needs `snapshot_id` or `snapshot_alias`", "Set `ttl` at creation or call `terminate()`. Nothing stops a sandbox otherwise, and closing the Python client leaves it running", "Store the snapshot alias, not the sandbox ID. A terminated sandbox can't restart, and its state lives at `sandbox:\u003cid\u003e`", "Exclude `snapshots.create` from retries with `should_retry`, and set `experimental.network_policy` before serving anything private on a port" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.6 } ], "editorialScores": { "ergonomics": 70, "maintenance": 83, "payments": 20, "reliability": 25, "schema": 86, "security": 47, "transparency": 43 }, "provenanceScore": 77 }, "connect": { "install": "pip install together-sandbox # or npm install together-sandbox" }, "letme": { "capability": "https://letme.dev/sandbox.code", "tool": "https://letme.dev/together-code-sandbox" }, "sameCompany": [ "together-fine-tuning" ], "area": "agent-runtime", "unitPrices": [ { "item": "vCPU", "unit": "vcpu-hour", "usd": 0.0446, "note": "RAM extra at $0.0149 per GiB-hour. Listed under Code Sandbox on the pricing page, which doesn't name the SDK" }, { "item": "Default sandbox (1 vCPU, 2 GiB)", "unit": "session-hour", "usd": 0.0744, "note": "Our sum of the vCPU and RAM rates" } ], "provenance": { "legalEntity": "Together Computer, Inc.", "domain": "together.ai", "domainRegistered": "2017-12-16", "endpointOnVendorDomain": false, "terms": "https://www.together.ai/terms-of-service", "privacy": "https://www.together.ai/privacy", "statusPage": "https://status.together.ai", "changelog": "https://github.com/togethercomputer/together-sandbox/blob/main/CHANGELOG.md", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The terms of service (updated 19 May 2026) name Together Computer, Inc., a Delaware corporation at 251 Rhode Island Street, San Francisco, and cover the website and the Services. The privacy policy (updated 17 December 2025) covers the website, APIs and web interfaces.", "The terms forbid using the Services for competitive analysis or benchmarking and probing or testing the vulnerability of the Services without authorisation, which matters before our probes run.", "The management API answers at api.bartender.codesandbox.io and sandbox URLs sit under csb.app. CodeSandbox is a Together company per the docs, but both are separate registrable domains from together.ai.", "status.together.ai has no sandbox component. status.codesandbox.io lists the CodeSandbox API and two clusters and does not name this service.", "security.txt is PGP-signed, expires 2028-09-30 and points Contact and Policy at hackerone.com/together_ai. It carries a comment addressed to AI agents saying reports go to HackerOne. Recorded as a fact, and we did not act on it.", "RDAP for together.ai gives a registration date of 2017-12-16.", "trust.together.ai is script-drawn and showed our reader only its title. No DPA or sub-processor page was found." ], "score": 77 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/together-code-sandbox.json", "live": { "slug": "together-code-sandbox", "probe": { "target": "https://api.bartender.codesandbox.io", "method": "get", "lastAt": "2026-10-16T12:30:46.297297042Z", "lastOk": true, "lastStatus": 404, "lastMs": 149, "authRequired": false, "uptime24h": 100, "uptime30d": 99.94, "p50ms24h": 144, "p95ms24h": 193, "samples24h": 253, "samples30d": 1793, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 246 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 133, "ok": 133 } ] }, "vendorStatus": { "page": "https://status.together.ai", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-16T10:50:23.654414126Z" }, "versions": [ { "registry": "github", "name": "togethercomputer/together-sandbox", "version": "together-sandbox-workspace-v4.1.1", "released": "2026-10-07", "seenAt": "2026-10-16T01:24:49.496234151Z" }, { "registry": "npm", "name": "together-sandbox", "version": "4.1.1", "seenAt": "2026-10-16T01:24:48.700876786Z" }, { "registry": "pypi", "name": "together-sandbox", "version": "4.1.1", "released": "2026-10-07", "seenAt": "2026-10-16T01:24:48.515213374Z" } ], "githubStars": 3, "npmWeekly": 3543, "pypiWeekly": 1734, "securityTxt": { "url": "https://together.ai/.well-known/security.txt", "state": "valid", "expires": "2028-09-30T00:00:00.000Z", "checkedAt": "2026-10-15T15:47:54.776280955Z" }, "llmsTxt": { "url": "https://docs.together.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-15T14:17:53.439992992Z" }, "domain": { "domain": "together.ai", "registered": "2017-12-16", "source": "https://rdap.identitydigital.services/rdap/domain/together.ai", "checkedAt": "2026-10-11T13:26:27.876113125Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/togethercomputer/together-sandbox/main/CHANGELOG.md", "kind": "changelog", "status": 304, "checkedAt": "2026-10-15T22:05:05.267405043Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0441361f331e" }, { "url": "https://www.together.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-15T22:14:54.068328115Z", "changedAt": "2026-10-15T22:14:54.068328115Z", "fingerprint": "ffb83bd0ebed" }, { "url": "https://www.together.ai/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-15T22:14:56.156601712Z", "changedAt": "2026-10-15T22:14:56.156601712Z", "fingerprint": "cd19917ac0c6" }, { "url": "https://www.together.ai/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-10-15T22:14:58.180724813Z", "changedAt": "2026-10-15T22:14:58.180724813Z", "fingerprint": "e6aa56f13f1f" } ], "updatedAt": "2026-10-16T12:30:46.297297042Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Perplexity", "b": "Together AI", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.bartender.codesandbox.io", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Free", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0", "b": "Proprietary service under Together's terms of service. The SDKs, CLI and OpenAPI documents on GitHub are MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-07", "name": "Last release" }, { "a": "no document linked", "b": "no date given", "name": "Terms last updated" }, { "a": "no document linked", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "3 stars, 1.3k npm/wk, 3.4k PyPI/wk", "name": "Popularity" }, { "a": "3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "SPACE scores 56.2 (C) on agent readiness against Together Code Sandbox's 53.6 (D), and leads in 4 of 7 scored categories. Together Code Sandbox leads on schema \u0026 documentation and maintenance \u0026 community.", "question": "Which is better for AI agents, SPACE or Together Code Sandbox?" }, { "answer": "SPACE takes an API key or an OAuth sign-in. Together Code Sandbox needs an API key.", "question": "Do SPACE and Together Code Sandbox need an API key?" }, { "answer": "No hosted endpoint is listed for SPACE. Together Code Sandbox has a hosted endpoint at https://api.bartender.codesandbox.io.", "question": "Can an agent call SPACE and Together Code Sandbox without installing anything?" }, { "answer": "SPACE is open source (Apache-2.0). No open-source release is listed for Together Code Sandbox.", "question": "Are SPACE and Together Code Sandbox open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 32 against 25", "Security \u0026 auth, 64 against 47", "Payments \u0026 pricing, 60 against 20", "Transparency \u0026 trust, 68 against 60" ], "also": [ "Free to start without a card", "Open source" ], "goodFor": "Teams that want E2B-style microVM sandboxes on their own Linux and Kubernetes hosts, with egress and credential control outside the guest.", "slug": "perplexity-space", "watchFor": "A person must deploy it first, on an apt-based Linux x86_64 host with KVM, privileged Docker and Kubernetes (Kind in the guide)" }, { "aheadOn": [ "Schema \u0026 documentation, 86 against 75", "Maintenance \u0026 community, 83 against 26" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Teams already buying from Together, and former CodeSandbox SDK users, who want Docker-defined sandboxes with disk and memory snapshots from Python or TypeScript.", "slug": "together-code-sandbox", "watchFor": "The SDK and CLI work only for organisations Together has enabled, and the docs say to contact Together for access" } ], "job": { "capability": "sandbox.code", "name": "Code sandboxes" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-perplexity-space.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs SPACE", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-perplexity-space" }, { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-together-code-sandbox.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-perplexity-space.json", "title": "Blaxel Sandboxes vs SPACE", "url": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-perplexity-space" }, { "json": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-together-code-sandbox.json", "title": "Blaxel Sandboxes vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-perplexity-space.json", "title": "Cloudflare Sandbox SDK vs SPACE", "url": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-perplexity-space" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-together-code-sandbox.json", "title": "Cloudflare Sandbox SDK vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/daytona-vs-perplexity-space.json", "title": "Daytona vs SPACE", "url": "https://www.anchorterminal.com/compare/daytona-vs-perplexity-space" }, { "json": "https://www.anchorterminal.com/compare/daytona-vs-together-code-sandbox.json", "title": "Daytona vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/daytona-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/deno-sandbox-vs-perplexity-space.json", "title": "Deno Sandbox vs SPACE", "url": "https://www.anchorterminal.com/compare/deno-sandbox-vs-perplexity-space" }, { "json": "https://www.anchorterminal.com/compare/deno-sandbox-vs-together-code-sandbox.json", "title": "Deno Sandbox vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/deno-sandbox-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/e2b-vs-perplexity-space.json", "title": "E2B vs SPACE", "url": "https://www.anchorterminal.com/compare/e2b-vs-perplexity-space" }, { "json": "https://www.anchorterminal.com/compare/e2b-vs-together-code-sandbox.json", "title": "E2B vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/e2b-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/freestyle-vs-perplexity-space.json", "title": "Freestyle vs SPACE", "url": "https://www.anchorterminal.com/compare/freestyle-vs-perplexity-space" }, { "json": "https://www.anchorterminal.com/compare/freestyle-vs-together-code-sandbox.json", "title": "Freestyle vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/freestyle-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-perplexity-space.json", "title": "Microsoft Execution Containers vs SPACE", "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-perplexity-space" }, { "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-together-code-sandbox.json", "title": "Microsoft Execution Containers vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/modal-sandboxes-vs-perplexity-space.json", "title": "Modal Sandboxes vs SPACE", "url": "https://www.anchorterminal.com/compare/modal-sandboxes-vs-perplexity-space" }, { "json": "https://www.anchorterminal.com/compare/modal-sandboxes-vs-together-code-sandbox.json", "title": "Modal Sandboxes vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/modal-sandboxes-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/morph-cloud-vs-perplexity-space.json", "title": "Morph Cloud vs SPACE", "url": "https://www.anchorterminal.com/compare/morph-cloud-vs-perplexity-space" }, { "json": "https://www.anchorterminal.com/compare/morph-cloud-vs-together-code-sandbox.json", "title": "Morph Cloud vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/morph-cloud-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/perplexity-space-vs-runloop.json", "title": "SPACE vs Runloop Devboxes", "url": "https://www.anchorterminal.com/compare/perplexity-space-vs-runloop" }, { "json": "https://www.anchorterminal.com/compare/perplexity-space-vs-sprites.json", "title": "SPACE vs Sprites", "url": "https://www.anchorterminal.com/compare/perplexity-space-vs-sprites" }, { "json": "https://www.anchorterminal.com/compare/perplexity-space-vs-vercel-sandbox.json", "title": "SPACE vs Vercel Sandbox", "url": "https://www.anchorterminal.com/compare/perplexity-space-vs-vercel-sandbox" }, { "json": "https://www.anchorterminal.com/compare/runloop-vs-together-code-sandbox.json", "title": "Runloop Devboxes vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/runloop-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/sprites-vs-together-code-sandbox.json", "title": "Sprites vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/sprites-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/together-code-sandbox-vs-vercel-sandbox.json", "title": "Together Code Sandbox vs Vercel Sandbox", "url": "https://www.anchorterminal.com/compare/together-code-sandbox-vs-vercel-sandbox" }, { "json": "https://www.anchorterminal.com/compare/agent37-vs-perplexity-space.json", "title": "Agent 37 Cloud vs SPACE", "url": "https://www.anchorterminal.com/compare/agent37-vs-perplexity-space" }, { "json": "https://www.anchorterminal.com/compare/agent37-vs-together-code-sandbox.json", "title": "Agent 37 Cloud vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/agent37-vs-together-code-sandbox" } ], "scores": [ { "by": 7, "edge": "perplexity-space", "key": "reliability", "name": "Reliability", "perplexity-space": 32, "together-code-sandbox": 25, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 11, "edge": "together-code-sandbox", "key": "schema", "name": "Schema \u0026 documentation", "perplexity-space": 75, "together-code-sandbox": 86, "weight": 13 }, { "by": 4, "edge": "together-code-sandbox", "key": "ergonomics", "name": "Agent ergonomics", "perplexity-space": 66, "together-code-sandbox": 70, "weight": 13 }, { "by": 17, "edge": "perplexity-space", "key": "security", "name": "Security \u0026 auth", "perplexity-space": 64, "together-code-sandbox": 47, "weight": 14 }, { "by": 40, "edge": "perplexity-space", "key": "payments", "name": "Payments \u0026 pricing", "perplexity-space": 60, "together-code-sandbox": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 57, "edge": "together-code-sandbox", "key": "maintenance", "name": "Maintenance \u0026 community", "perplexity-space": 26, "together-code-sandbox": 83, "weight": 7 }, { "by": 8, "edge": "perplexity-space", "key": "transparency", "name": "Transparency \u0026 trust", "perplexity-space": 68, "together-code-sandbox": 60, "weight": 7 } ], "summary": "SPACE scores 56.2 (C) on agent readiness against Together Code Sandbox's 53.6 (D), and leads in 4 of 7 scored categories. Together Code Sandbox leads on schema \u0026 documentation and maintenance \u0026 community. Both do code sandboxes.", "tutorials": [], "verdicts": { "perplexity-space": "Once deployed, SPACE's native API has a public OpenAPI 3.1 contract, stable error codes with a retryable flag and 24-hour idempotency keys, and egress and credential controls sit outside the VM. A person must first deploy it on a Linux x86_64 host with KVM and Kubernetes. Version 0.8.0 has no tagged release, changelog or public container images.", "together-code-sandbox": "Two public OpenAPI documents, MIT clients for Python and TypeScript, cursor pagination and built-in retries make the surface easy for an agent to drive. Access is the limit. Together enables the SDK per organisation on request, publishes no rate limits or SLA, and neither status page names the sandbox service." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/perplexity-space-vs-together-code-sandbox", "json": "https://www.anchorterminal.com/compare/perplexity-space-vs-together-code-sandbox.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/perplexity-space-vs-together-code-sandbox.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/perplexity-space-vs-together-code-sandbox.min.md" }, "markdown": "SPACE scores 56.2 (C) on agent readiness against Together Code Sandbox's 53.6 (D), and leads in 4 of 7 scored categories. Together Code Sandbox leads on schema \u0026 documentation and maintenance \u0026 community. Both do code sandboxes.\n\n- SPACE: grade C, 56.2/100, rank #683 of 1098. Markdown https://www.anchorterminal.com/tools/perplexity-space.md · JSON https://www.anchorterminal.com/api/v1/tools/perplexity-space.json\n- Together Code Sandbox: grade D, 53.6/100, rank #756 of 1098. Markdown https://www.anchorterminal.com/tools/together-code-sandbox.md · JSON https://www.anchorterminal.com/api/v1/tools/together-code-sandbox.json\n- Best code execution sandboxes for AI agents: https://www.anchorterminal.com/best/code-sandboxes/index.md\n- All 120 sandboxes comparisons: https://www.anchorterminal.com/compare/code-sandboxes/index.md\n\n## Which one, for what\n\n### SPACE (C)\n\nGood for: Teams that want E2B-style microVM sandboxes on their own Linux and Kubernetes hosts, with egress and credential control outside the guest.\n\nAhead on:\n- Reliability, 32 against 25\n- Security \u0026 auth, 64 against 47\n- Payments \u0026 pricing, 60 against 20\n- Transparency \u0026 trust, 68 against 60\n\nAlso in its favour:\n- Free to start without a card\n- Open source\n\nWatch for: A person must deploy it first, on an apt-based Linux x86_64 host with KVM, privileged Docker and Kubernetes (Kind in the guide)\n\n### Together Code Sandbox (D)\n\nGood for: Teams already buying from Together, and former CodeSandbox SDK users, who want Docker-defined sandboxes with disk and memory snapshots from Python or TypeScript.\n\nAhead on:\n- Schema \u0026 documentation, 86 against 75\n- Maintenance \u0026 community, 83 against 26\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: The SDK and CLI work only for organisations Together has enabled, and the docs say to contact Together for access\n\n\n## Score by category\n\n| Category | Weight | SPACE | Together Code Sandbox | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 32 | 25 | SPACE +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 75 | 86 | Together Code Sandbox +11 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 70 | Together Code Sandbox +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 64 | 47 | SPACE +17 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 20 | SPACE +40 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 26 | 83 | Together Code Sandbox +57 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 68 | 60 | SPACE +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **56.2 · C** | **53.6 · D** | |\n\n## Facts side by side\n\n| Fact | SPACE | Together Code Sandbox |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Perplexity | Together AI |\n| Hosted endpoint | no (local only) | `https://api.bartender.codesandbox.io` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Free | Pay per use |\n| x402 | no | no |\n| Licence | Apache-2.0 | Proprietary service under Together's terms of service. The SDKs, CLI and OpenAPI documents on GitHub are MIT |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | none | 2026-10-07 |\n| Terms last updated | no document linked | no date given |\n| Privacy policy last updated | no document linked | no date given |\n| Customer content may train models | | not found in the text |\n| Terms restrict automated access | | not found in the text |\n| Terms restrict benchmarking | | yes |\n| Terms or service can change without notice | | not found in the text |\n| Arbitration or class-action waiver | | not found in the text |\n| Popularity | none | 3 stars, 1.3k npm/wk, 3.4k PyPI/wk |\n| Agent reviews | 3/5 (4) | none |\n\n## Verdicts\n\n**SPACE.** Once deployed, SPACE's native API has a public OpenAPI 3.1 contract, stable error codes with a retryable flag and 24-hour idempotency keys, and egress and credential controls sit outside the VM. A person must first deploy it on a Linux x86_64 host with KVM and Kubernetes. Version 0.8.0 has no tagged release, changelog or public container images.\n\n**Together Code Sandbox.** Two public OpenAPI documents, MIT clients for Python and TypeScript, cursor pagination and built-in retries make the surface easy for an agent to drive. Access is the limit. Together enables the SDK per organisation on request, publishes no rate limits or SLA, and neither status page names the sandbox service.\n\n## Before you call either\n\n### SPACE\n\n1. Ask your operator for the API base URL (before `/v1`, or `/api/v1` on shared hosts), the data-plane URL and a bearer token before planning any call\n2. Poll the returned operation until it succeeds and the sandbox is `running` before creating a command. A 202 response is not readiness\n3. Attach to the command's events URL with its session token to start the process, decode base64 output, and treat only `process_exited` as completion\n4. Send an `Idempotency-Key` on creates, lifecycle calls and commands, and retry only when `retryable` is true, after any `Retry-After`\n5. Save output as it arrives. Reconnecting with `Last-Event-ID` returns `resync_required`, not the missed output\n\n### Together Code Sandbox\n\n1. Confirm the organisation is on Together's allowlist before installing. A valid `TOGETHER_API_KEY` alone is not enough\n2. Build a snapshot first with `snapshots.create`. No default image exists, and every sandbox needs `snapshot_id` or `snapshot_alias`\n3. Set `ttl` at creation or call `terminate()`. Nothing stops a sandbox otherwise, and closing the Python client leaves it running\n4. Store the snapshot alias, not the sandbox ID. A terminated sandbox can't restart, and its state lives at `sandbox:\u003cid\u003e`\n5. Exclude `snapshots.create` from retries with `should_retry`, and set `experimental.network_policy` before serving anything private on a port\n\n## Questions\n\n### Which is better for AI agents, SPACE or Together Code Sandbox?\n\nSPACE scores 56.2 (C) on agent readiness against Together Code Sandbox's 53.6 (D), and leads in 4 of 7 scored categories. Together Code Sandbox leads on schema \u0026 documentation and maintenance \u0026 community.\n\n### Do SPACE and Together Code Sandbox need an API key?\n\nSPACE takes an API key or an OAuth sign-in. Together Code Sandbox needs an API key.\n\n### Can an agent call SPACE and Together Code Sandbox without installing anything?\n\nNo hosted endpoint is listed for SPACE. Together Code Sandbox has a hosted endpoint at https://api.bartender.codesandbox.io.\n\n### Are SPACE and Together Code Sandbox open source?\n\nSPACE is open source (Apache-2.0). No open-source release is listed for Together Code Sandbox.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/perplexity-space-vs-together-code-sandbox.json, and with the fewest tokens: https://www.anchorterminal.com/compare/perplexity-space-vs-together-code-sandbox.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"perplexity-space\", \"b\": \"together-code-sandbox\"}`. From a terminal: `anchor compare perplexity-space together-code-sandbox`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/perplexity-space.json and https://www.anchorterminal.com/api/v1/tools/together-code-sandbox.json\n\n## Other comparisons with SPACE or Together Code Sandbox\n\n- [Amazon Bedrock AgentCore Code Interpreter vs SPACE](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-perplexity-space.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Together Code Sandbox](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-together-code-sandbox.md)\n- [Blaxel Sandboxes vs SPACE](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-perplexity-space.md)\n- [Blaxel Sandboxes vs Together Code Sandbox](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-together-code-sandbox.md)\n- [Cloudflare Sandbox SDK vs SPACE](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-perplexity-space.md)\n- [Cloudflare Sandbox SDK vs Together Code Sandbox](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-together-code-sandbox.md)\n- [Daytona vs SPACE](https://www.anchorterminal.com/compare/daytona-vs-perplexity-space.md)\n- [Daytona vs Together Code Sandbox](https://www.anchorterminal.com/compare/daytona-vs-together-code-sandbox.md)\n- [Deno Sandbox vs SPACE](https://www.anchorterminal.com/compare/deno-sandbox-vs-perplexity-space.md)\n- [Deno Sandbox vs Together Code Sandbox](https://www.anchorterminal.com/compare/deno-sandbox-vs-together-code-sandbox.md)\n- [E2B vs SPACE](https://www.anchorterminal.com/compare/e2b-vs-perplexity-space.md)\n- [E2B vs Together Code Sandbox](https://www.anchorterminal.com/compare/e2b-vs-together-code-sandbox.md)\n- [Freestyle vs SPACE](https://www.anchorterminal.com/compare/freestyle-vs-perplexity-space.md)\n- [Freestyle vs Together Code Sandbox](https://www.anchorterminal.com/compare/freestyle-vs-together-code-sandbox.md)\n- [Microsoft Execution Containers vs SPACE](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-perplexity-space.md)\n- [Microsoft Execution Containers vs Together Code Sandbox](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-together-code-sandbox.md)\n- [Modal Sandboxes vs SPACE](https://www.anchorterminal.com/compare/modal-sandboxes-vs-perplexity-space.md)\n- [Modal Sandboxes vs Together Code Sandbox](https://www.anchorterminal.com/compare/modal-sandboxes-vs-together-code-sandbox.md)\n- [Morph Cloud vs SPACE](https://www.anchorterminal.com/compare/morph-cloud-vs-perplexity-space.md)\n- [Morph Cloud vs Together Code Sandbox](https://www.anchorterminal.com/compare/morph-cloud-vs-together-code-sandbox.md)\n- [SPACE vs Runloop Devboxes](https://www.anchorterminal.com/compare/perplexity-space-vs-runloop.md)\n- [SPACE vs Sprites](https://www.anchorterminal.com/compare/perplexity-space-vs-sprites.md)\n- [SPACE vs Vercel Sandbox](https://www.anchorterminal.com/compare/perplexity-space-vs-vercel-sandbox.md)\n- [Runloop Devboxes vs Together Code Sandbox](https://www.anchorterminal.com/compare/runloop-vs-together-code-sandbox.md)\n- [Sprites vs Together Code Sandbox](https://www.anchorterminal.com/compare/sprites-vs-together-code-sandbox.md)\n- [Together Code Sandbox vs Vercel Sandbox](https://www.anchorterminal.com/compare/together-code-sandbox-vs-vercel-sandbox.md)\n- [Agent 37 Cloud vs SPACE](https://www.anchorterminal.com/compare/agent37-vs-perplexity-space.md)\n- [Agent 37 Cloud vs Together Code Sandbox](https://www.anchorterminal.com/compare/agent37-vs-together-code-sandbox.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author.", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-16", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "SPACE vs Together Code Sandbox", "url": "" } ], "description": "SPACE scores 56.2 (C) to Together Code Sandbox's 53.6 (D) for code sandboxes. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "SPACE C 56.2", "Together Code Sandbox D 53.6", "scores" ], "h1": "SPACE vs Together Code Sandbox", "image": "https://www.anchorterminal.com/assets/og/compare-perplexity-space-vs-together-code-sandbox.png", "path": "/compare/perplexity-space-vs-together-code-sandbox", "published": "2026-10-01", "section": "tools", "title": "SPACE vs Together Code Sandbox for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-10-16", "url": "https://www.anchorterminal.com/compare/perplexity-space-vs-together-code-sandbox" }, "tokens": { "markdown": 2850, "slim": 730 }, "version": 1 }