All resourcesPlanning catalog · 2026-11-05.1
Start with the workflow and its authority.
Use these four illustrative templates to name the actor, source systems, evidence and action boundary. They describe work to implement and accept; they do not connect customer systems or execute a hosted action.
Read the JSON catalogGET https://www.jextra.com/api/v1/templates
Insurance
Connected policyholder servicing
Give a servicing employee or authorized broker policy and claim context, then prepare the next service request.
Authority boundary: Coverage decisions, claim adjudication, settlement and payment need separately defined authority. This example prepares a service request.
Acceptance questions
- Resolve current access: Revoked and unrelated identities receive no policyholder evidence.
- Retrieve policy and claim context: Each returned fact retains its source identifier and effective date; mismatched records escalate.
- Retrieve supporting documents: Evidence is filtered by access and cannot change tool authority.
- Prepare a service request: A retry returns the same request; external communication requires the agreed approval.
Retail and commerce
Agent-assisted quote to order
Let a customer's assistant check account pricing and availability, then prepare a quote or order.
Authority boundary: An availability response does not reserve stock. Ordering, credit, payment and reservation authority must be agreed separately.
Acceptance questions
- Resolve account entitlement: A buyer cannot retrieve another account's prices or quotes.
- Retrieve current price and stock: Unit, currency, account and freshness mismatches prevent an actionable quote.
- Check product requirements: Unconfirmed compatibility is shown as unresolved and never invented.
- Prepare a quote: Retries do not duplicate the quote, and purchase authority remains explicit.
Financial services
Evidence-backed reconciliation
Gather records from both sides of a reconciliation and prepare an exception case for an analyst.
Authority boundary: This workflow investigates and prepares a case. Posting, write-offs, transfers and payments require separate authority.
Acceptance questions
- Resolve analyst assignment: An unassigned identity receives no account evidence.
- Compare reconciliation records: Missing and duplicate keys, date rules and currency mismatches are explicit exceptions.
- Retrieve source evidence: Each comparison links to the original source and relevant time period.
- Prepare an exception case: Retries preserve a single case; no ledger or payment action is inferred.
Software platforms
Agent-enabled product onboarding
Let an authorized customer's agent configure a workspace, validate an import and prepare a provisioning job.
Authority boundary: Tenant creation, billing changes, destructive imports and production activation follow explicit product permissions and approval policy.
Acceptance questions
- Resolve tenant entitlement: Revoked membership and cross-tenant requests return no tenant evidence.
- Validate workspace configuration: Unsupported settings and entitlements produce actionable validation errors.
- Preview the import: Invalid rows and duplicate keys are reported before any production import.
- Prepare a provisioning job: A repeated request returns one job and cannot change another tenant.
Use the catalog with your team or agent.
The JSON response retains the stable template IDs insurance-service, commerce-quotes, finance-exceptions and software-onboarding. Read its systems, dependencies, capabilities, measures and boundaries before drafting a scope. Capability paths inside a template are proposed interfaces for that project, not endpoints hosted by this website.
The catalog is read-only and requires no account. Use the separate claims-intake reference for a runnable local contract and tests. Customer API availability, current permissions, source completeness and release approval need their own evidence.