Scope (Legal)

List the legal-services categories Scope can dispatch matters to. Each category has a slug, human label, and an indicator of whether vendors expose REST APIs (api_native) or are reached through Scope's ops-backed adapters (ops_backed).

No parameters. Call it with no arguments.

List Scope-verified vendors available for hire. Use this tool when the user wants to see, browse, or compare vendors they could hire for legal work. Specifically: court reporters, process servers, records firms, IMEs, expert witnesses, and every other legal-services category....

Hire any human vendor for legal work, from inside the user's AI. Use this tool whenever the user needs to hire, find, book, get, or dispatch a legal-services vendor. Specifically: process servers, court reporters, records retrieval firms, IMEs, expert witnesses, e-discovery ve...

Look up a matter by its display id (e.g. SC-2041) or UUID. Returns scope details, instant rate-card quotes (rate_card model) or bids (legacy bid model), award status, deliverables, and the conflict_check + approval state. For anonymized matters, vendor names are redacted in re...

List the firm's matters and their dispatch status. Use this tool when the user asks about active or historical matters, dispatches, or pipeline. Specifically: open matters, awarded matters, in-progress work, completed matters, or matters for a given client. Triggers include: '...

List the calling buyer org's vendor roster. Returns each vendor with their tier (primary | backup | excluded), optional category scoping, notes, and lock window. Use to answer questions like 'who's on my roster for court reporting?' or 'what vendors do we currently exclude?' b...

No parameters. Call it with no arguments.

Add or update a vendor on the buyer's roster. Use to set a vendor as primary, backup, or excluded - optionally scoped to a single service category. Examples: 'mark Capitol Reporters as primary for court reporting,' 'add MES Solutions to my IME roster as backup,' 'exclude this...

Remove a vendor from the buyer's roster entirely. Use when the relationship has changed and you want to revert the vendor to neutral marketplace status (no priority routing, no exclusion). Requires authentication.

Award a dispatched matter to a chosen vendor. Locks the booking, notifies the vendor (push + email), and schedules a Stripe Connect invoice that fires when the matter completes (buyer review auto-accepts at 5 days). Returns a confirmation payload with actions taken and accurat...

Reschedule an already-awarded project to a new date. Use only when the project is in an active engagement state (post-award, pre-delivery). Returns the confirmed new slot and whether the vendor was notified. Disallowed source states return a typed error (project_already_delive...

Give the user a status briefing on their Scope vendor activity. Use this tool when the user asks what is happening, what changed, or wants a status update on their dispatches. Triggers include: 'what is happening on Scope', 'give me a briefing', 'what changed this week', 'rece...

Complete activity log for a single scope. Returns the append-only event chain: dispatched, quotes received, awarded, accepted, calendar set, work completed, invoice paid. Useful for compliance review or matter-record export.

Show the firm's vendor spend, sliced by dimension. Use this tool when the user asks how much the firm has spent on vendors. Specifically: spend by vendor, by service category, by matter type, by jurisdiction, by client, by matter, or over a time window. Triggers include: 'show...

Per-vendor credential, insurance, and on-time status across your roster. Returns COI / W-9 / insurance expiry, BAA status, 90-day on-time percentage, total awarded engagements, and an alerts list per vendor.

Vendors with expiring or expired credentials. Filtered version of scope_vendor_health. Use for compliance review or for the morning briefing's 'what needs attention' list.

Search the buyer org's structured conflict-party log across every scope. Use for an OCG / Rule 1.7 prior-representation check before dispatching new work. Filter by party name (case-insensitive substring), optional party_type, and optional lookback window. Returns the scopes w...

Read-only view of the roster auto-routing state machine for one scope. Returns the current state (pending_primary, awaiting_primary_response, primary_accepted, primary_declined, primary_timed_out, opened_to_network, awarded, completed), the Primary vendor for the dispatch (whe...

Show typical market pricing for a legal-services vendor category. Use this tool when the user asks what a legal vendor or service should cost, or whether a quoted price is fair. Specifically: process serving, court reporting, records retrieval, IMEs, expert witnesses, e-discov...

List vendor-uploaded deliverables for a scope. Returns each deliverable with type, vendor name, upload date, file size, notes, version, secure-link URL (works without login, expires in 7 days), and a short-lived signed download URL (1 hour TTL). Caller must own the scope (buye...

Fetch a single vendor-uploaded deliverable by id. Returns metadata + a short-lived signed download URL (1 hour TTL). The buyer's AI can hand the URL to a downstream analysis tool (transcript review, exhibit extraction, etc.) - Scope is the delivery layer, not the analysis layer.

Search the buyer org's deliverables by free-text query. v1 uses SQL ILIKE on notes + deliverable_type fields; full-text search (tsvector + GIN) is a follow-up. Optional scope_id narrows to a single scope; optional deliverable_type narrows to one type (e.g., 'Transcript', 'COI'...

Ad-hoc re-send of an existing deliverable to additional recipients across one or more channels. Use when a lead attorney wants to forward a transcript, or to push a report to a CMS matter id, or to re-fan-out after fixing a typo in the email recipient list. Buyer org members o...

Submit an initial scope of work to a legal vendor for negotiation. Use when a user wants to engage a vendor for specific legal work but the spec may need vendor input to finalize.

Vendor asks the buyer clarifying questions about a proposed scope. Use when the work spec is ambiguous or missing details a bid would depend on.

Buyer answers vendor clarifying questions and submits an updated work spec.

Vendor submits a bid against a proposed scope. Response envelope includes a gate descriptor when a human approval is required before the bid can be accepted.

Buyer counters a vendor bid with a new amount and updated terms. Vendor must re-bid with scope_bid for the session to advance.

Accept the current bid and move the session to ACCEPTED. If a human gate has not cleared, returns gate_pending with an approval URL.

Reject the current session. Terminal. Either party can call. Reason is a structured enum.

Read-only. Returns current state, gate state, work spec, and current bid for a session. Caller must be a participant.