API & MCP
Connect to Kunkafa
Connect once. Then ask Kunkafa about your market from the AI app you already use.
1. Add Kunkafa
Add this address in your AI app’s MCP or connector settings.
https://kunkafa.com/mcp2. Sign up or sign in
A Kunkafa page opens in your browser. Create an account or sign in, then approve the connection.
3. Ask about your market
Return to your AI app to explore the data, ask questions and continue your learning and research.
Choose your AI app
Requires an AI app with remote MCP support. Check your provider’s plan and setup guide.
ChatGPT
Set up a custom app in ChatGPT web developer mode, then select it in the conversation. Provider plan and workspace restrictions apply.
Provider setup instructionsClaude
Add a custom connector with the Kunkafa MCP URL in Claude settings and complete browser authorization. Check your account’s connector availability.
Provider setup instructionsGemini
Custom apps are configured on Gemini web where available. Google currently limits this feature by account, region and language; it is not available to every Gemini user. Gemini CLI has a separate MCP setup.
Provider setup instructionsGrok
Use a custom remote connector where your Grok account or workspace supports it. If the connector controls are missing, check the provider’s account requirements.
Provider setup instructionsOpenClaw
Add Kunkafa as an outbound MCP server in your OpenClaw installation and use its browser OAuth login. There is no universal OpenClaw app-opening link.
Provider setup instructionsOther MCP-compatible app / Grokbot
Confirm that your particular app supports remote MCP and browser OAuth. “Grokbot” does not identify a verified connector here; use your app’s documented setup, never paste account credentials into chat.
Provider setup instructionsTry asking
Use Kunkafa to explain what could happen in my chosen market. Show both directions and explain Kunkafa’s confidence.
Start with a market file
Open a market in Kunkafa and choose “Take the conversation to your favorite AI app”. Prepare and download its file, attach it in your AI app, then paste the supplied question. No custom connector is needed. File-upload availability depends on your AI app.
The file contains dated market summaries in both directions, available historical performance and up to 10 published results, with guidance and public source links. It is a snapshot; prepare a new file for updated private data. Opening an AI app does not attach the file automatically.
Advanced: custom MCP setup
Connect Kunkafa once in your AI app. Sign up or sign in and approve access in your browser, then return to the conversation to explore your market and continue your learning and research.
Pro API setup
In Account → API & MCP connections, choose Create API token. Give it a recognizable name and select only the permissions you need. The token is shown once and expires after 90 days.
Keep the token in your application’s secret storage. Send it in the Authorization: Bearer header. Never put it in a URL, public website bundle, screenshot, support message or shared source file. The example below assumes KUNKAFA_TOKEN is already set securely.
curl --fail-with-body \
--header "Authorization: Bearer ${KUNKAFA_TOKEN}" \
"https://kunkafa.com/api/v1/usage?locale=en"
Permissions and discovery
The read scopes are markets:read, outlooks:read, performance:read, results:read and usage:read. A token must include the scope for its requested operation. Token permissions never extend your account’s market or plan access.
Market and usage lists are paginated. Follow page.nextCursor until it is null; do not assume the first page contains every permitted market. The default page size is 20, with a maximum of 50. Restart without a cursor if access or market names change.
OAuth client details
Use authorization code flow with PKCE and resource https://kunkafa.com/mcp. Discovery starts at https://kunkafa.com/.well-known/oauth-protected-resource/mcp; the authorization issuer is https://kunkafa.com/oauth. Use the endpoints returned by discovery and validate the issuer, resource and audience.
Access tokens expire after 10 minutes. Refresh tokens rotate, expire after 30 days without use or 90 days overall, and reuse invalidates the connection’s grant. Refreshing a token does not take over an active session.
Canonical API endpoints
REST requires a Pro API token. Use GET for discovery, usage and the published record; use POST with a JSON body containing markets and locale for summaries. Replace {slug} with the market value returned by discovery.
GET https://kunkafa.com/api/v1/markets
POST https://kunkafa.com/api/v1/outlooks
GET https://kunkafa.com/api/v1/markets/{slug}/performance
GET https://kunkafa.com/api/v1/markets/{slug}/results
GET https://kunkafa.com/api/v1/usage
MCP tools
- list_markets
Available markets
List markets this connection can read. Follow page.nextCursor until null for all permitted markets; full names are preserved. Free MCP includes only the account’s chosen market.
- get_outlooks
Kunkafa summaries
Read both directions across up to three published durations. Reading private summaries makes this connection the active session. Check returned usage and retry times; do not repeatedly retry an exhausted allowance.
- get_performance
Historical performance
Read published performance and sample counts for an authorized market. Historical performance is separate from Kunkafa’s confidence.
- get_results
Previous results
Read at most ten published results for an authorized market. Selected results are not the full history or an aggregate performance claim.
- get_usage
Usage and limits
Check remaining request, concurrency and rolling summary allowances. The permitted-market list is paginated; follow page.nextCursor until null. Does not consume a summary allowance or take over the active session.
Signup and plans tools
get_plans lists plans and current pricing links. get_account_links provides browser links for signup, sign-in, subscription and account management. These two tools do not require an account.