Is Toknbase an AI agent or a secrets manager?

Both — the vault is the engine, the agent is the product. Toknbase is an AI SecOps agent that actively scans repos, fixes exposed secrets, opens PRs, verifies every fix, and logs each action with a tamper-evident on-chain receipt. The vault stores secrets with zero-knowledge encryption so even the agent cannot read the values it protects.

What can the AI SecOps agent do?

The agent scans public and private GitHub repos for exposed credentials, monitors continuously on every new commit, proposes fix PRs to replace hardcoded secrets with secure runtime calls, verifies fixes are gone after application, checks whether found credentials have appeared in known breach databases, and sends a weekly CISO briefing with your full security posture. Every action is logged on-chain with a cryptographic receipt.

Can Toknbase — or its employees — read my secrets?

No. Client-side encryption means we store only ciphertext. We never have your encryption key. Even a Toknbase engineer with direct canister access would only see encrypted bytes. This is a cryptographic guarantee, not a policy promise.

How do I use Toknbase with AI agents like Claude or Cursor?

Toknbase provides a hosted MCP (Model Context Protocol) endpoint at https://4wj64-piaaa-aaaan-q5q7q-cai.icp0.io/mcp. Add it to your Claude Desktop, Cursor, or Windsurf config as a JSON block — no installation, no npm package, no local server required.

What is the pricing for Toknbase?

Toknbase offers three plans: Free ($0 — 1 seat, 50 secrets, 3 scans/month, free forever), Pro ($19.99/seat/month or $15.99/seat/month billed annually — unlimited seats, private repo scanning, AI auto-remediation, full MCP endpoint, pre-commit hook), and Enterprise ($499.99/month flat — everything in Pro plus SSO/SAML, custom detectors, dedicated support, DPA, and 99.9% SLA). Annual billing saves 20% on Pro.

Can I change plans at any time?

Yes — upgrade, downgrade, or cancel at any time. Upgrades take effect immediately. Downgrades apply at the next billing cycle.

Is there a free trial?

The Free plan is free forever and includes public repo scanning and an on-chain audit trail — no credit card required. Pro and Enterprise plans can be started immediately with a paid subscription.

How does Toknbase compare to Doppler or HashiCorp Vault?

Three key differences: (1) It's an AI agent, not a passive vault — it actively watches repos, finds leaks, and opens fix PRs without being asked. (2) Zero-knowledge encryption — Toknbase cryptographically cannot read your secrets, even under subpoena. (3) On-chain audit trail — every agent action has a tamper-evident cryptographic receipt. No other secrets management tool provides all three.

How is Toknbase different from using .env files?

.env files store secrets on disk in plaintext and are frequently committed to version control by accident. Toknbase encrypts secrets in your browser before they leave your device, stores only ciphertext, actively scans your repos for accidentally exposed values, and can automatically open a fix PR when it finds one. It's a proactive agent, not a static file.

Can Toknbase scan private GitHub repos?

Yes. Public repos can be scanned instantly with no signup. To scan private repos, connect your GitHub account via OAuth — Toknbase requests the minimum required permissions and uses a short-lived access token. Private repo scanning is included in the Pro plan.

What happens if a secret is exposed in an old commit?

Removing a secret from a file does not remove it from git history — anyone with access to the repository can still find it in old commits. Toknbase scans git history for exposed secrets, not just the current state of the code. When it finds one, it flags it as a historical exposure and recommends rotating the credential immediately, since it must be treated as compromised.

REFERENCE

API Reference

REST endpoints and MCP tool reference for all Toknbase integrations.

openapi.json Swagger UIOpenAPI 3.1

Overview REST Endpoints MCP Tools Token Scopes Chain Verification

Overview

Every API request requires an Authorization header

Requests without this header return401 Unauthorized. Get your agent token from Dashboard → Tokens → Service Identities. Every example in this reference requires this header.

Authentication header

curl https://4wj64-piaaa-aaaan-q5q7q-cai.icp0.io/api/secrets \
 -H"Authorization: Bearer YOUR_AGENT_TOKEN"

Where to get your token:Dashboard → Tokens → Service Identities → Create new token. Choose the minimum scope your use case requires. The examples below omit the header for brevity — it is always required.

Toknbase exposes two integration surfaces: a REST HTTP API for CI/CD pipelines and shell scripts, and 14 MCP tools for AI editor integrations. Base URL:https://4wj64-piaaa-aaaan-q5q7q-cai.raw.icp0.io

REST Endpoints

GET/api/secret

Get a single secret by name. Returns the plaintext value.

Parameters

Name	Type	Required	Description	Example
`name`	string	required	The secret name to retrieve	`DATABASE_URL`

Request

curl -s -X GET \
 -H"Authorization: Bearer $TOKNBASE_AGENT_TOKEN" \
"https://4wj64-piaaa-aaaan-q5q7q-cai.raw.icp0.io/api/secret"

Response

{
  "name": "DATABASE_URL",
  "value": "postgres://user:pass@host/db",
  "environment": "production"
}

Response Schema

Field	Type	Description
`name`	string	The secret name
`value`	string	The plaintext secret value (decrypted)
`environment`	string	Environment tag (production, staging, etc.)

GET/api/secrets

List all secret names accessible by this token. Values are not returned.

Request

curl -s -X GET \
 -H"Authorization: Bearer $TOKNBASE_AGENT_TOKEN" \
"https://4wj64-piaaa-aaaan-q5q7q-cai.raw.icp0.io/api/secrets"

Response

{
  "secrets": [
    "DATABASE_URL",
    "STRIPE_KEY",
    "OPENAI_API_KEY"
  ]
}

Response Schema

Field	Type	Description
`secrets`	string[]	Array of accessible secret names (no values)

POST/api/secrets

Create a new secret.

Parameters

Name	Type	Required	Description	Example
`name`	string	required	Secret name (alphanumeric, underscores, hyphens)	`NEW_API_KEY`
`value`	string	required	The secret value to store	`sk-live-abc123xyz`
`environment`	string	optional	Environment tag (production, staging, development)	`production`

Request

curl -s -X POST \
 -H"Authorization: Bearer $TOKNBASE_AGENT_TOKEN" \
 -H"Content-Type: application/json" \
 -d '{"name":"MY_SECRET","value":"..."}' \
"https://4wj64-piaaa-aaaan-q5q7q-cai.raw.icp0.io/api/secrets"

Response

{
  "ok": true,
  "id": "sec_abc123"
}

Response Schema

Field	Type	Description
`ok`	boolean	true if the secret was created successfully
`id`	string	The internal ID of the new secret

PUT/api/secrets/:name

Update an existing secret value.

Parameters

Name	Type	Required	Description	Example
`name`	string	required	Secret name in the URL path (e.g. DATABASE_URL)	`DATABASE_URL`
`value`	string	required	New secret value to replace the existing one	`postgres://newuser:newpass@host/db`

Request

curl -s -X PUT \
 -H"Authorization: Bearer $TOKNBASE_AGENT_TOKEN" \
 -H"Content-Type: application/json" \
 -d '{"name":"MY_SECRET","value":"..."}' \
"https://4wj64-piaaa-aaaan-q5q7q-cai.raw.icp0.io/api/secrets/:name"

Response

{
  "ok": true
}

Response Schema

Field	Type	Description
`ok`	boolean	true if the update was applied successfully

DELETE/api/secrets/:name

Delete a secret permanently.

Parameters

Name	Type	Required	Description	Example
`name`	string	required	Secret name in the URL path (e.g. DATABASE_URL)	`DATABASE_URL`

Request

curl -s -X DELETE \
 -H"Authorization: Bearer $TOKNBASE_AGENT_TOKEN" \
"https://4wj64-piaaa-aaaan-q5q7q-cai.raw.icp0.io/api/secrets/:name"

Response

{
  "ok": true
}

Response Schema

Field	Type	Description
`ok`	boolean	true if the secret was deleted. Returns 404 if not found.

Warning

Secret values are returned in plaintext via the REST API. Always use HTTPS and treat agent tokens as secrets themselves. Rotate tokens regularly.

MCP Tools

The@toknbase/mcp-serverexposes 15 tools over the Model Context Protocol. Connect it to Cursor, Claude Code, Windsurf, VS Code, or Cline.

Tool	Description
toknbase_list_secrets	Lists all secret names accessible to the token
toknbase_get_secret	Gets a secret by name, returning its plaintext value (for MCP-enabled secrets)
toknbase_create_secret	Creates a new secret
toknbase_update_secret	Updates an existing secret
toknbase_delete_secret	Deletes a secret
toknbase_search_secrets	Searches secrets by name pattern
toknbase_batch_create_secrets	Creates multiple secrets in one call
toknbase_get_audit_log	Retrieves the audit log
toknbase_list_team_secrets	Lists secrets shared with a team
toknbase_rotate_secret	Rotates a secret value
toknbase_create_folder	Creates a folder for organizing secrets
toknbase_list_folders	Lists all folders
toknbase_assign_folder	Assigns a secret to a folder
toknbase_get_token_info	Gets info about the current agent token

Important

MCP-enabled secrets are decrypted by the MCP server using the agent token as the key. The AI agent receives the plaintext value for any secret the user has explicitly enabled for agent access. Zero-knowledge refers to Toknbase servers — not the agent. Only enable MCP access for secrets your AI tools actually need.

Token Scopes

Every agent token is created with a scope that determines what operations it can perform.

Scope	Allows	Recommended for
`read_only`	List and search secrets, read metadata	AI editors that only need to reference secrets
`read_write`	Create, update, delete secrets	CI/CD pipelines, automation
`full_access`	All operations including rotation and folder management	Trusted automation systems

Audit Chain Verification

Publicly verify any audit export against the live canister state — no account required.

GET/api/verifypublic · no auth required

Verify a chain tip hash against the canister's certified state. Returns whether the hash matches the current audit chain root committed to ICP certified variables.

Query Parameters

Parameter	Required	Description
`hash`	required	The`chainTipHash`value from a Toknbase compliance export

Request

curl"https://4wj64-piaaa-aaaan-q5q7q-cai.raw.icp0.io/api/verify?hash=abc123def456"

Response — verified

{
  "verified": true,
  "canisterId": "4wj64-piaaa-aaaan-q5q7q-cai",
  "timestamp": 1712000000000000000,
  "entriesCount": 1247
}

Response — not verified

{
  "verified": false,
  "canisterId": "4wj64-piaaa-aaaan-q5q7q-cai",
  "timestamp": 1712000000000000000,
  "entriesCount": 1247
}

Note

You can also verify using the browser-based verifier attoknbase.net/verify— paste any exported chain tip hash and get an instant result, no account needed.

Important

This endpoint is backed by ICP certified variables — the canister's chain tip hash is committed to the ICP subnet's certified state on every audit event. The response is cryptographically verifiable against the ICP network public key.

What's next

Error Reference

HTTP errors and agent token error codes.

MCP / AI Agents

Set up your AI editor in under 2 minutes.

Was this page helpful?