# Read-only access to your company’s OKRs.

> Org API keys give read-only access to your company’s OKRs — the same town square every teammate can see. Free. No writes. No AI wallet debit.

Agent index: https://gahmbit.com/llms.txt
HTML page: https://gahmbit.com/developers

An org API key lets a script or agent read what every teammate can already see. Keys cannot write, and they never debit the AI wallet. No subscription.

Create a key (org admins): https://app.gahmbit.com/settings?tab=integrations

## What a key is

Keys are org-scoped and start with fok_. They authenticate as the organization, not as a person. Org comes from the key — you do not need to send X-Org-Id (if you do, it must match).

Any org admin can mint a key. Every member can see that keys exist. There is no partner program and no plan to unlock this. Rate limits are ops guardrails, not billing.

## How to authenticate

Send the secret as a bearer token. Copy the REST base URL from Settings → Integrations (Connection). Browser JavaScript from other websites will not work — the app origin is allowlisted. Use curl, a server, or a local agent client.

```
Authorization: Bearer $GAHMBIT_API_KEY

# REST base — copy from Settings → Integrations
```

## REST (live)

GET and HEAD only. The same org-visible resources a member can read: people, coverage (including Missing), cycles, objectives, key results, check-ins, comments, and the Company activity feed.

```
curl -sS \
  -H "Authorization: Bearer $GAHMBIT_API_KEY" \
  "$GAHMBIT_REST_BASE/objectives"
```

## MCP (coming soon)

Model Context Protocol support for Cursor, Claude, and other agents is coming soon. Use the REST base URL from Settings → Integrations today — same org API key, same read-only town-square data.

When MCP ships, Settings will list the endpoint and we will document one-click setup. The planned tool list below matches the read surface we intend to expose over MCP.

## What a key cannot do

Writes return 403 KEY_READ_ONLY. Keys cannot create or edit OKRs, post check-ins, or comment.

They cannot call the AI service — no agents, no coaching, no wallet debit. They cannot act as you (GET /people/me, My Feed). They cannot manage the org, billing, or Slack from a key. One key is one org.

## Preview, not a platform SKU

This is a documented preview of the free-core read path — not a versioned public API and not a homepage product. Paths and MCP tool names may change. We do not publish the full internal OpenAPI.

Create and revoke keys under Settings → Integrations. Admins mint; members can see the inventory.

## Planned MCP tools

REST is live. MCP is coming soon. These names match the read surface intended for MCP.

| Tool | REST path |
| --- | --- |
| list_people | /people |
| get_coverage | /coverage |
| list_cycles | /cycles |
| get_cycle | /cycles/{id} |
| list_objectives | /objectives |
| get_objective | /objectives/{id} |
| list_key_results | /key-results |
| get_key_result | /key-results/{id} |
| list_check_ins | /key-results/{keyResultId}/check-ins |
| list_comments | /comments |
| list_events | /events |
