A unified digital network

Documentation

ACCESS Documentation

Find your way around ACCESS, manage your account, and explore the workspace API. Can't find what you need? Contact support.

Quickstart

From account to first request.

  1. 01

    Create your account

    Create your account and follow the workspace onboarding steps.

    Get started
  2. 02

    Create a scoped key

    Create a key in Developer settings and keep it in your server environment.

    Developer settings
  3. 03

    Make your first request

    Send the key as a Bearer token and read back your handle and permissions.

    See the example

Getting started

Platform modules

JYSON — AI intelligence

Gifts and billing

Account and security

Workspace API

Live · Beta

Start in Developer settings to create a scoped API key. Send it in the Authorization header as a Bearer token. Keep keys in your server environment, never in public browser code or a shared repository. Revoke a key in Developer settings when you no longer need it.

The beta API currently exposes these routes. Each request acts as the identity that owns the key.

GET
/api/v1/customersScope: readList your workspace customers.
POST
/api/v1/customersScope: customers:writeCreate a customer in your workspace with explicit write permission and an Idempotency-Key header.
GET
/api/v1/meScope: Valid keyRead your ACCESS handle and granted scopes. Vault summaries require the read scope.
GET
/api/v1/vault/search?q=your-queryScope: readSearch excerpts from your synced vault content.
POST
/api/v1/jyson/askScope: jysonSend a JSON question for a JYSON response.
GET
/api/v1/modelsScope: jysonList models supported by the Zin gateway.
POST
/api/v1/chat/completionsScope: jysonUse the OpenAI-compatible chat format with the Zin gateway.

Download the OpenAPI reference →

Make your first request

curl https://getaccess.world/api/v1/me -H "Authorization: Bearer $ACCESS_API_KEY"

A successful identity response includes ok, handle, scopes, and vaults. New keys expire within 90 days; choose a shorter lifetime in Developer settings. Existing keys retain their current expiry policy. Revoke a key immediately if it is exposed. Requests are limited to 120 per minute per key, with 10 intelligence requests per minute. A 429 response includes Retry-After. Missing, expired, or revoked keys return an authentication error; a key without a required scope cannot use that endpoint. Vault results require synced content. JYSON requests also depend on the deployment's model configuration and usage controls.

Can't find what you need?