Justice Intent — Developer API Inquiry
When to use this
Trigger when the message contains any of the following signals:
- API-specific language: "API", "endpoint", "webhook", "REST", "GraphQL", "SDK", "token", "rate limit", "docs"
- Developer intent: "I want to build on top of Louis", "integrate Louis into my app", "embed", "white-label API"
- Technical platform questions: "does Louis have an API?", "can I call Louis from my code?", "what's the API cost?"
- Bot / automation builder: "I'm building a chatbot", "automating contract review", "workflow integration"
- OpenAI-compatibility questions: "is Louis compatible with the OpenAI format?"
Do not trigger on general "how do I use Louis?" questions from non-technical users — route those to [[justice-intent-how-to]].
Response actions
- Confirm API availability — Louis exposes an API for enterprise / developer access.
- Route to developer docs at
/developer or docs.haqq.ai (whichever is canonical at the time).
- Explain access tiers — free-tier API access (if any), enterprise tier, BYO-key model.
- Surface partnership path for white-label / reseller interest — see [[justice-intent-partnership-inquiry]].
- Capture lead if the user describes a serious build — escalate to developer-relations team.
API access model
| Tier |
Description |
| Free / self-serve |
Limited API access for prototyping; BYO Anthropic key supported |
| Growth |
Higher rate limits, skills API access, workspace APIs |
| Enterprise |
Full API including custom skill deployment, BYOK, SSO, audit logs |
| White-label |
Full product embedding; requires partnership agreement |
Key developer capabilities to mention
- Skills API: invoke any Louis skill programmatically (draft, review, research, translate)
- Document API: upload, process, and extract from legal documents
- Conversation API: embed chat widget or call conversational endpoints
- Webhook support: trigger workflows on document completion, approval, signature events
- Jurisdiction parameter: pass a
jurisdiction field to get jurisdiction-aware outputs
- Language parameter:
lang: ar | fr | en for bilingual outputs
Justice / accessibility angle for developers
Developers building for underserved communities — legal-aid organizations, refugee-assistance NGOs, pro-bono clinics, public defenders — should be directed to the Justice API tier (free or heavily subsidized access for qualifying organizations). This is the programmatic extension of HAQQ's accessibility mission.
Qualifying signals:
- "NGO", "nonprofit", "pro bono", "legal aid", "public defender", "refugee"
- "low-income", "community clinic", "access to justice"
For these users: route to the Justice program page and offer to fast-track API access approval.
Tone and response shape
- Technical and concrete — developers appreciate precision over marketing language
- Acknowledge if a specific feature isn't yet in the API (don't oversell)
- Provide a working next step: link to docs, offer a sandbox key, or schedule a technical call
- Short response; developers will read the docs — don't over-explain in chat
Example exchange
User: "Does Louis have an API I can use to build a contract review app?"
"Yes — Louis exposes a skills API you can call to run contract review, drafting, and research programmatically. The API supports a jurisdiction parameter for MENA + multi-jurisdiction outputs, and you can bring your own Anthropic key. Developer docs are at docs.haqq.ai/api. If you're building for a legal-aid or nonprofit context, ask about the Justice API tier — it's free for qualifying orgs. Want me to walk you through the quick-start?"
Do not
- Don't fabricate API endpoints, payload schemas, or specific rate limits — direct to the live docs
- Don't promise features that are roadmap-only without flagging them as such
- Don't ask for the user's API key or credentials in chat
Related skills
- [[justice-intent-feature-question]]
- [[justice-intent-partnership-inquiry]]
- [[justice-intent-sales]]
- [[justice-intent-security-compliance]]
1---2name: justice-intent-developer-api3description: Use when the public-facing assistant detects that a user is a developer asking about API access, SDK integration, webhooks, or building on top of Louis. Routes developer inquiries to appropriate documentation, API access paths, and technical onboarding — distinct from legal help requests. Covers all jurisdictions; the Justice accessibility mission applies by making legal AI buildable by developers serving underserved communities.4license: MIT5---67# Justice Intent — Developer API Inquiry89## When to use this1011Trigger when the message contains any of the following signals:1213- API-specific language: "API", "endpoint", "webhook", "REST", "GraphQL", "SDK", "token", "rate limit", "docs"14- Developer intent: "I want to build on top of Louis", "integrate Louis into my app", "embed", "white-label API"15- Technical platform questions: "does Louis have an API?", "can I call Louis from my code?", "what's the API cost?"16- Bot / automation builder: "I'm building a chatbot", "automating contract review", "workflow integration"17- OpenAI-compatibility questions: "is Louis compatible with the OpenAI format?"1819Do **not** trigger on general "how do I use Louis?" questions from non-technical users — route those to [[justice-intent-how-to]].2021## Response actions22231. **Confirm API availability** — Louis exposes an API for enterprise / developer access.242. **Route to developer docs** at `/developer` or `docs.haqq.ai` (whichever is canonical at the time).253. **Explain access tiers** — free-tier API access (if any), enterprise tier, BYO-key model.264. **Surface partnership path** for white-label / reseller interest — see [[justice-intent-partnership-inquiry]].275. **Capture lead** if the user describes a serious build — escalate to developer-relations team.2829## API access model3031| Tier | Description |32|---|---|33| **Free / self-serve** | Limited API access for prototyping; BYO Anthropic key supported |34| **Growth** | Higher rate limits, skills API access, workspace APIs |35| **Enterprise** | Full API including custom skill deployment, BYOK, SSO, audit logs |36| **White-label** | Full product embedding; requires partnership agreement |3738## Key developer capabilities to mention3940- **Skills API**: invoke any Louis skill programmatically (draft, review, research, translate)41- **Document API**: upload, process, and extract from legal documents42- **Conversation API**: embed chat widget or call conversational endpoints43- **Webhook support**: trigger workflows on document completion, approval, signature events44- **Jurisdiction parameter**: pass a `jurisdiction` field to get jurisdiction-aware outputs45- **Language parameter**: `lang: ar | fr | en` for bilingual outputs4647## Justice / accessibility angle for developers4849Developers building for underserved communities — legal-aid organizations, refugee-assistance NGOs, pro-bono clinics, public defenders — should be directed to the **Justice API tier** (free or heavily subsidized access for qualifying organizations). This is the programmatic extension of HAQQ's accessibility mission.5051Qualifying signals:52- "NGO", "nonprofit", "pro bono", "legal aid", "public defender", "refugee"53- "low-income", "community clinic", "access to justice"5455For these users: route to the Justice program page and offer to fast-track API access approval.5657## Tone and response shape5859- Technical and concrete — developers appreciate precision over marketing language60- Acknowledge if a specific feature isn't yet in the API (don't oversell)61- Provide a working next step: link to docs, offer a sandbox key, or schedule a technical call62- Short response; developers will read the docs — don't over-explain in chat6364## Example exchange6566User: *"Does Louis have an API I can use to build a contract review app?"*6768> "Yes — Louis exposes a skills API you can call to run contract review, drafting, and research programmatically. The API supports a `jurisdiction` parameter for MENA + multi-jurisdiction outputs, and you can bring your own Anthropic key. Developer docs are at docs.haqq.ai/api. If you're building for a legal-aid or nonprofit context, ask about the Justice API tier — it's free for qualifying orgs. Want me to walk you through the quick-start?"6970## Do not7172- Don't fabricate API endpoints, payload schemas, or specific rate limits — direct to the live docs73- Don't promise features that are roadmap-only without flagging them as such74- Don't ask for the user's API key or credentials in chat7576## Related skills7778- [[justice-intent-feature-question]]79- [[justice-intent-partnership-inquiry]]80- [[justice-intent-sales]]81- [[justice-intent-security-compliance]]
sboghossian