The San Francisco Compute Company
The San Francisco Compute Company (SF Compute) runs large-scale, vetted GPU clusters and operates a compute marketplace where buyers reserve H100/H200 capacity by the hour and sellers resell unused compute back into the market with no long-term lock-in. Its public preview REST API (api.sfcompute.com, base path /preview/v2) and the `sf` CLI let developers buy and sell compute via orders and an orderbook, manage pools of reserved balance, launch and operate GPU instances from images and templates, run procurements and deployments, and organize resources across workspaces with roles, grants, and tags. Authentication is a Bearer token (sk_live_ API key). The API is documented on a Mintlify docs site with a per-operation OpenAPI reference, an llms.txt index, and an official agent skill.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles The San Francisco Compute Company the way a machine reads it — 18 machine-readable artifacts across 14 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — The San Francisco Compute Company scores 55.8/100 (developing), with a separate agent-readiness read of 78/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile The San Francisco Compute Company
Each block below is one kind of artifact we hold for The San Francisco Compute Company. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 14
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
The San Francisco Compute Company Account API
The authenticated account and logged-in user.
The San Francisco Compute Company Deployments API
Deployment automations that maintain a fleet of instances, including spot deployments that buy capacity up to a maximum price.
The San Francisco Compute Company Feature Flags API
The Feature Flags API from The San Francisco Compute Company — 2 operation(s) for feature flags.
The San Francisco Compute Company Images API
Custom machine images for instances.
The San Francisco Compute Company Instance SKU Catalog API
Browse available instance SKU property definitions.
The San Francisco Compute Company Instance SKUs API
The Instance SKUs API from The San Francisco Compute Company — 4 operation(s) for instance skus.
The San Francisco Compute Company Instance Templates API
Reusable instance configuration.
The San Francisco Compute Company Instances API
Spin up instances in a capacity to use your available compute.
The San Francisco Compute Company Orderbook API
Read-only orderbook visibility: bid/ask spread, depth, open and filled orders, and historical fills, keyed on hardware requirements + delivery window.
The San Francisco Compute Company Orders API
Estimate an order before placing it: filled price, fee, and operational notices.
The San Francisco Compute Company Pools API
A bucket of owned compute balance over time.
The San Francisco Compute Company Procurements API
Market automations that maintain capacity by placing buy/sell orders.
The San Francisco Compute Company Users API
Read-only access to users within the caller's organization.
The San Francisco Compute Company Workspaces API
Resource containers scoped to an account.
Scroll within the panel for all 14 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
The San Francisco Compute Company Agentic Access
65 operations · 31 acting · 2 human-in-the-loop
AGENTICResources
Every other property we hold for The San Francisco Compute Company — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 6
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/the-san-francisco-compute-company · machine-readable index on apis.io