Kepler Documentation
Select a document from the sidebar to get started.
Kepler Developer Portal
Access the Kepler developer portal — API client registration, documentation, and tooling. Requires read access to postman-cs/kepler-infra.
Kepler Dev Portal
1
Register
2
Get Token
3
First Call
4
Agent (Optional)
Step 1: Register a Service Client
Create an OAuth client with the scopes you need. Not sure which scopes? Pick a preset below.
Step 2: Get a JWT Token
Exchange your client credentials for a Bearer token. Copy and run this command:
bash
curl -s -X POST https://api.kepler.rip/v1/auth/service-token \
-H "Content-Type: application/json" \
-d '{"client_id": "YOUR_CLIENT_ID", "client_secret": "YOUR_SECRET"}'Then export the token:
bash
export TOKEN="paste-your-access_token-here"Step 3: Make Your First API Call
Try one of these requests based on your scopes:
Getting a 401 or 403? Check the Diagnostics tab for troubleshooting.
Step 4: Create Your First Agent (Optional)
Register a named agent with versioned config. Requires kepler:agents:write scope.
✓
You're All Set!
Your client is registered and you've made your first API call.
Features
What Kepler provides for agent builders and platform consumers. Every feature below is backed by live infrastructure, tests, and documentation.
Mint New Client
My Service Clients
Loading...
No clients registered yet.
| Name | Client ID | Scopes | Created | Last Used | Status |
|---|
Endpoints
Select an endpoint from the sidebar to see scoped curl and grpcurl snippets.
Scope & Permission Check
Paste a JWT token or select a client to see its granted scopes and what endpoints are accessible.
Integration Smoke Tests
Tests API behavior correctness: rate limit headers, search edge cases, and concurrent request handling. For uptime monitoring, use the Platform Status tab.
Error Troubleshooting
Select the HTTP status code you're seeing to get resolution steps.
Operator Quick Reference
Common operational commands for incident response and debugging. Replace placeholder variables before running.
API Health
Live health check against /v1/health. Auto-refreshes every 30 seconds.
Checking...
SLO Dashboard
Service Level Objectives and current status. Click "Run Checks" to measure live latency against targets.
Error Budget Policy
| Budget Consumed | Action |
|---|---|
| < 50% | Normal operations. Deploy freely. |
| 50–75% | Reduce deploy frequency. Prioritize reliability. |
| 75–90% | Feature freeze. Only reliability and bug fixes. |
| > 90% | Incident mode. All hands on reliability. |
Kepler Almanac (MCP)
The Kepler Almanac MCP server connects coding assistants (Cursor, Claude Code, OpenAI Codex CLI, and others) to Kepler data: customers, communications, briefs, product gaps, Confluence, Jira, and team tools. It uses service client credentials to mint scoped API tokens and expose Kepler data to coding assistants over MCP.
1. Configure Credentials
Paste existing Kepler credentials or click "Generate" to provision an MCP service client for your GitHub account.
2. Add to your assistant
Copy the configuration for your preferred assistant. Node 18+ is required.
npm package: The configuration uses npx -y -p @kepler-project/almanac@latest -c almanac to fetch and run the server dynamically.
Lost secret? If you forget your generated Client Secret, click "Generate Credentials" again to revoke the old one and issue a new pair.
Client Registered
Save these credentials now. The client secret cannot be retrieved later.
Token caching
Tokens expire after 1 hour. Store your
Tokens expire after 1 hour. Store your
client_id and client_secret securely — not the token.
Request a new token on 401 responses. A 55-minute cache window avoids boundary-condition failures.
Revoke Client
Are you sure you want to revoke ? This action cannot be undone.