The San Francisco Compute Company · Authentication Profile

The San Francisco Compute Company Authentication

Authentication

SF Compute's public preview API authenticates with a Bearer token. Create an API token with `sf tokens create --name ` (or in the dashboard at https://sfcompute.com/account/api-keys); the token is shown once and starts with `sk_live_`. Tokens begin with no permissions - grant access per resource with `sf grants create --token --role --workspace ` (see Roles and Grants). For scripts, set the SF_BEARER_TOKEN or SF_API_KEY environment variable. Send the token as `Authorization: Bearer sk_live_...`.

The San Francisco Compute Company secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyGPUComputeCloud InfrastructureArtificial IntelligenceMachine-LearningCompute MarketplaceResellingInfrastructure
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearer_auth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: openapi/the-san-francisco-compute-company-openapi.json
docs: https://docs.sfcompute.com/preview/tokens
summary:
  types:
  - http
  http_schemes:
  - bearer
description: >-
  SF Compute's public preview API authenticates with a Bearer token. Create an
  API token with `sf tokens create --name <name>` (or in the dashboard at
  https://sfcompute.com/account/api-keys); the token is shown once and starts
  with `sk_live_`. Tokens begin with no permissions - grant access per resource
  with `sf grants create --token <name> --role <role> --workspace <workspace>`
  (see Roles and Grants). For scripts, set the SF_BEARER_TOKEN or SF_API_KEY
  environment variable. Send the token as `Authorization: Bearer sk_live_...`.
schemes:
- name: bearer_auth
  type: http
  scheme: bearer
  bearerFormat: JWT
  token_prefix: sk_live_
  create_via:
  - 'CLI: sf tokens create --name <name>'
  - 'Dashboard: https://sfcompute.com/account/api-keys'
  env_vars:
  - SF_BEARER_TOKEN
  - SF_API_KEY
  authorization_model: role + grant per workspace/resource (see https://docs.sfcompute.com/preview/roles and https://docs.sfcompute.com/preview/grants)
  description: Bearer token sent as Authorization header. Create via `sf tokens create` or the dashboard API keys page.
  sources:
  - openapi/the-san-francisco-compute-company-openapi.json

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/the-san-francisco-compute-company-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.