Krish Agent

Documentation

The API is a versioned JSON service at https://agentone.mtandaolabs.com/v1. The public pages on this host are documentation and legal notices; they do not call the API automatically.

Quick start

  1. Sign in with Google at /v1/auth/google/start. The callback shows a device token once; store it securely.
  2. Check the credential:
    curl https://agentone.mtandaolabs.com/v1/me \
      -H "Authorization: Bearer krish_dt_..."
  3. List provider presets:
    curl https://agentone.mtandaolabs.com/v1/providers/catalog \
      -H "Authorization: Bearer krish_dt_..."
  4. Create a provider, test the connection, and import its models. See the full contract in the repository.

Authentication

Protected endpoints take Authorization: Bearer krish_dt_<43 base64url characters>. Tokens are stored only as SHA-256 hashes and can be revoked per device. The bootstrap credential (X-Bootstrap-Token) is accepted only for pairing and provider management and belongs to the primary owner account.

Google sign-in requests only openid email profile. It does not request Drive, Gmail, YouTube, or Docs access.

Endpoints

MethodPathPurpose
GET/v1/healthLiveness and version
GET/v1/auth/google/startBegin Google sign-in
GET/v1/auth/google/callbackFinish sign-in and show a device token
GET/v1/meCurrent account and device
POST/v1/devices/pairCreate a short-lived pairing code
POST/v1/devices/pair/completeExchange a pairing code for a device token
GET/v1/devicesList devices for the account
DELETE/v1/devices/:idRevoke a device
GET/v1/providers/catalogList built-in provider presets
GET / POST/v1/providersList or create providers
GET / PATCH / DELETE/v1/providers/:idRead, update, or delete a provider
POST/v1/providers/:id/testTest the upstream connection
POST/v1/providers/:id/models/discoverImport models reported by the provider
GET / POST/v1/providers/:id/modelsList or add models
PATCH / DELETE/v1/providers/:id/models/:modelIdUpdate or remove a model

Limits

Data and security

Accounts, devices, provider configuration, encrypted credentials, models, tests, and audit events are stored in Cloudflare D1. Tokens, pairing codes, and rate-limit buckets are stored as hashes. See the repository documents for the full API contract, data model, and security model.

No chat, task execution, or tool-calling endpoint exists yet, so the documentation describes only the current surface.