> ## Documentation Index
> Fetch the complete documentation index at: https://docs.outreign.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Capabilities by interface

> Exactly what the app, REST API, MCP and webhooks can and cannot do, so you pick the right one before you build.

OutReign has four interfaces. They share the same account and data but expose different actions. Check this table before designing an integration or giving an AI agent a task.

## Capability matrix

| Capability | OutReign app | REST API | MCP (AI assistants) | Webhooks |
| - | - | - | - | - |
| Search for **new** prospects by ICP | Yes | `POST /prospects/search` | `search_prospects` | No |
| Find company names/domains | Yes | `POST /companies/search` | `search_companies` | No |
| Look up a known person | Yes | `POST /people/lookup` | `find_person` | No |
| Verify an email address on its own | During search/enrichment and agent chat | `POST /email/verify` | `verify_email` | No |
| List and read saved leads | Yes | `GET /leads`, `GET /leads/{id}` | `list_leads` | — |
| Search saved leads by text | Yes | No (filter by `industry`/`status`) | `search_leads` | — |
| Create and update saved leads | Yes | `POST /leads`, `PATCH /leads/{id}` | `create_lead`, `update_lead` | Inbound `lead.created` / `lead.updated` |
| Bulk import leads | CSV import | `POST /leads/bulk` (100 per request) | No | — |
| Delete saved leads | Yes | `DELETE /leads/{id}` | No | — |
| Enrich a saved lead | Yes | `POST /leads/{id}/enrich` | `enrich_lead` | — |
| Research a saved lead | Yes | `POST /leads/{id}/research` | `research_lead` | — |
| Score a lead against your ICP | Yes | `POST /leads/{id}/score` | `score_lead` | — |
| Generate an email draft | Yes | `POST /email/generate` | `generate_email` | — |
| Enroll a lead in a sequence | Yes | No | `enroll_lead_in_sequence` | — |
| Reply to an inbox thread | Yes | No | `send_reply` (queues the reply) | — |
| Read sent emails and replies | Yes | No | `list_recent_sent_emails`, `list_recent_replies` | — |
| Deals | Yes | Full create/read/update/delete | `list_deals`, `update_deal` | `deal.*` events |
| Activities and contacts | Yes | Full create/read/update/delete | No | Inbound `contact.created` |
| ICP profiles | Yes | `POST /workspace/actions` | `list_icp_profiles`, `update_icp_profile`, `workspace_action` | — |
| AI SDR agent settings and stats | Yes | No | `update_agent_config`, `get_agent_stats` | — |
| Get notified when data changes | — | — | — | Outbound `lead.*`, `deal.*` |

Campaign templates/briefs/objections, signals, mailbox health, reply tagging, sequence pause/resume and outbound statistics are also available through `POST /workspace/actions` and MCP `workspace_action`. See [workspace actions](https://docs.outreign.io/developer-docs/workspace-actions.md) for action fields and confirmation behavior.

## What this means for AI agents

Discovery and intelligence actions reuse the app's real handlers, identity checks, credits and limits. A typical agent workflow is:

1. Find new prospects with `search_prospects` / `POST /prospects/search`; these are not saved automatically.
2. Check an address with `verify_email` / `POST /email/verify`. Only `verified: true` confirms a mailbox; catch-all, role and unknown results remain unproven.
3. Save approved prospects with `create_lead` / `POST /leads`, then enrich, research, score and draft.
4. Ask the user before enrolling a lead or sending a reply.

`search_leads` still searches saved CRM records; `search_prospects` searches the external B2B network. Do not invent results or treat a failed request as an empty successful search. The table above is the current contract, not a claim that every app settings/admin screen is available remotely.

## Credits and plan limits

* API and MCP access require a paid plan (Starter and above). See [errors and limits](https://docs.outreign.io/developer-docs/errors-and-limits.md) for request allowances.
* Enrichment and email generation use the same account entitlements as the app. An API key never bypasses plan limits.
* Request allowances (per minute / per day) and feature credits are separate balances.
* Paid prospect searches cost no reveal credits but count against the same daily search meter; results are capped by plan (Starter 25, Growth 50, Pro 100, Agency 200).
* Person lookup and saved-lead enrichment retain the app's one-credit reserve/refund behavior.
* Standalone verification charges no reveal credit, with 10 requests/minute and rolling daily checks capped at your plan's daily search limit. API, MCP and agent chat share this verification allowance.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.