Support

Track selection

• Agent Kai API: use this lane for PKM discovery, consent requests, consent status, REST, and MCP questions.
• Agentic APIs: use this lane for /api/a2a, MuleSoft agent chains, profile enrichment, browser-proxy testing, and CRM activation workflows.

What to include in a support request

• Organization name and environment.
• The exact track: Agent Kai API or Agentic APIs.
• The endpoint path or MCP route you called.
• For Agentic APIs, include sessionId, id, and the returnedupstreamStatus when available.
• For Kai, include the discovered scope, consent request id, or the latest consent-status response.

Common issues and fixes

400 Invalid JSON-RPC

Cause: malformed A2A payload or missing JSON-RPC structure. Fix: validate the request body and resend.

401 Unauthorized

Cause: invalid credentials, expired token, or missing authorization. Fix: rotate credentials and confirm the right runtime lane.

500 Internal agent error

Cause: upstream agent failed or timed out. Fix: retry with backoff and include the request identifiers in your support note.

Consent mismatch

Cause: Kai scope was never discovered or a broader grant is being assumed incorrectly. Fix: discover first, request the exact scope, then re-check consent status.

Debugging tips

• Use /api/a2a/{agent} only for browser-safe testing in the Agentic lane.
• Call direct MuleSoft endpoints from your backend only.
• Use /developers/agent-kai when the problem involves PKM, consent, REST, or MCP.
• Use /developers/agentic-apis when the problem involves A2A, enrichment, or activation flows.