Scope (Legal)

Award a dispatched matter to a chosen vendor. Locks the booking, generates the engagement letter, triggers calendar coordination, and prepares the Stripe Connect invoice. Returns a confirmation payload with the actions taken and next steps. Demo mode does not actually fire downstream integrations - the response shape is real but no DocuSign envelope, no Stripe invoice, no calendar invite goes out.

Briefing for the authenticated buyer org's recent matter activity. Returns matters bucketed by action_required (awaiting your decision), awaiting_vendor (open, no quote yet), scheduled_this_week, scheduled_next_week, and recently_completed. Use this at session start to ground your AI on what's changed since last view.

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 where the party appears, the matched entries on each scope, and a total count.

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.

Post a new matter to Scope. Vendors in the requested category return anonymized quotes via the interactive SWP negotiation flow (propose / clarify / refine / bid / counter / accept). Returns the matter id and status; bids close after bid_window_minutes (default 4 days). Requires a valid Scope API token. Use this when an AI workflow needs to engage a vendor on behalf of a firm - for example when a deposition notice arrives, when records retrieval is needed, or when an e-discovery request is triggered.

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.

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 (when set), routing timestamps, time remaining until network fallback, and bid count. Use to answer 'is my Primary going to take this or are we opening it up?' in a single tool call.

Look up a matter by its display id (e.g. SC-2041) or UUID. Returns scope details, bids received, award status, and any deliverables. For sealed matters, vendor names are anonymized in returned bids until the matter is awarded.

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).

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 (buyer) or have a bid on it (vendor).

List matters in flight for the calling buyer organization. Useful for status sweeps and pipeline reporting from inside an AI workflow.

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?' before dispatching a matter.

List Scope-verified vendors. Each result includes verified-reputation metrics (on-time %, budget variance, rework rate, completed matters, satisfaction) and credentialing summary. Vendor names are returned only for verified callers; anonymous callers get anonymized labels.

Return distribution stats (min / p25 / median / p75 / p90 / max / mean) on awarded-bid amounts across the platform cohort for a given service category and optional jurisdiction. Privacy gate: cohorts under 10 awarded bids across different buyer orgs return cohort_too_small instead of stats. Individual bid amounts and vendor names are never returned.

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.

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.

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', 'Report').

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 only.

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 vendor entirely.' Requires authentication.

Aggregate awarded-bid spend across the buyer org over a date window. Group by vendor, category, matter_type, jurisdiction, or scope. Returns total amount + per-group breakdown sorted by spend descending.

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.

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

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.

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 counters a vendor bid with a new amount and updated terms. Vendor must re-bid with scope_bid for the session to advance.

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.

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

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.