---
name: iblai-connect-lexisnexis
description: "Read LexisNexis data through the Lexis APIs (Protégé API, REST APIs, CourtLink API, Lex Machina API, State Net API, Law360 API) and expose it to an ibl.ai agent as an MCP tool. Use when the user asks an agent to work with LexisNexis data, or to set up a LexisNexis MCP connection on ibl.ai."
metadata:
  kind: guide
---

# LexisNexis connector for AI agents

> A starting point maintained on ibl.ai at https://ibl.ai/developer/connectors/lexisnexis — not part of the iblai/vibe repository. Checked against LexisNexis' documentation on October 20, 2026; test it against your own LexisNexis setup before you rely on it.

LexisNexis provides legal research content: case law, statutes, regulations, secondary materials, Practical Guidance, news, court dockets (CourtLink), litigation analytics (Lex Machina) and legislative tracking (State Net).

## Auth & conventions

- **API:** Lexis APIs (Protégé API, REST APIs, CourtLink API, Lex Machina API, State Net API, Law360 API) (REST). Licensed REST and Cognitive APIs with JSON: Protégé 'Ask' and 'Summarize' with citations, legal and news search and retrieval with alerts, CourtLink dockets, Lex Machina analytics and State Net legislation.
- **Access:** Partner or license program. License-gated. Organizations request access through LexisNexis; once approved they get credentials and onboarding for the LexisNexis Developer Portal (dev.lexisnexis.com) with docs and a sandbox. Pricing depends on products and volume.
- **Auth:** OAuth 2.0. LexisNexis states its REST, Cognitive and Protégé APIs use OAuth authentication with role-based access, firm-wide throttling and audit logging. Grant types and endpoints are documented only inside the gated portal.
- Keep LexisNexis credentials in environment variables or the ibl.ai credential store. Never print a token in chat and never commit one to a file.
- Destructive or outward-facing calls are marked **Confirm with the user first** — do.

## Reads

- **Protégé answers** — 'Ask' and 'Summarize' return answers with citations grounded in primary law, secondary materials and Practical Guidance.
- **Legal and news content** — Search and retrieve legal and news content; set alerts for new content.
- **Court dockets** — CourtLink API: federal and state filings, docket updates and case tracking.
- **Litigation analytics** — Lex Machina API: judges, attorneys, parties, resolutions, damages and timing.
- **Legislation and regulation** — State Net API: bills, regulations, agency documents, ordinances and ballot measures.

## Writes

- None. This skill only reads LexisNexis data.

## Expose it to an ibl.ai agent (MCP)

LexisNexis did not publish an MCP server of its own when this skill was checked. Host a small MCP server that wraps the calls above, then register it below.

First install the ibl.ai platform skills and connect your organization (writes `IBLAI_ORG`, `IBLAI_USERNAME` and `IBLAI_API_KEY` to `.env`):

```bash
npx skills add iblai/vibe --all
# then, in your coding agent:
/iblai-api-login
```

Every call below sends `Authorization: Api-Token $IBLAI_API_KEY`.

1. **Register the server** — `POST https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/mcp-servers/` with `name`, `url`, `transport` (`sse` | `websocket` | `streamable_http`) and `auth_type` (`none` | `token` | `oauth2`). Capture the returned `id`.
   - For an API key or service credential use `auth_type=token` with `auth_scope=platform` for one key across the organization, or scope it to a single agent for one key per agent.
2. **Create the connection** — `POST https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/mcp-server-connections/` with `server`, `scope` (`platform` | `mentor` | `user`), `auth_type`, and either `credentials` + `authorization_scheme` or a `connected_service` id for OAuth. Credentials are masked on read; never send a masked value back.
3. **Enable it on the agent** — `GET https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/mentors/{agent_id}/settings/`, add `mcp-tool` to `tool_slugs` and the server id to `mcp_servers`, then `PATCH` the full lists back. They are replaced, not merged.

Full reference: https://ibl.ai/developer/platform/mcp/mcp-connections and the `/iblai-api-agent-mcp` skill.

## Example prompts

- "Summarize the leading New York cases on piercing the corporate veil since 2020, with citations"
- "Track new docket entries in the Acme v. Beta case in S.D.N.Y."
- "How often does Judge Smith grant summary judgment in patent cases?"
- "Alert me to new state bills on biometric privacy"

## Guardrails

- Research queries and uploaded matter facts can reveal client strategy and are attorney work product; keep them confidential and out of shared logs.
- Request the narrowest LexisNexis scopes or role the task needs, and prefer a read-only credential for agents that only answer questions.
- Return the fields the user asked for, not whole records; do not paste personal data into chat that the user did not request.
- Before any write, show the user exactly what will change and wait for a yes.
- Page through large result sets and back off on rate-limit responses instead of retrying in a loop.

## References

- Lexis APIs product page: https://www.lexisnexis.com/en-us/products/lexis-api.page
- LexisNexis Developer Portal: https://dev.lexisnexis.com/
- This connector on ibl.ai: https://ibl.ai/developer/connectors/lexisnexis
- ibl.ai MCP server connections: https://ibl.ai/developer/platform/mcp/mcp-connections