request response35–50 min2 stages8 code languages

Contract slice: Evidence-led claims from incident to settlement

Faster, more consistent claims decisions with tamper-aware spatial evidence.

The real-world moment

After a severe storm, a policyholder submits vehicle-damage images and location evidence. The insurer must guide capture, detect missing or contradictory context without overclaiming authenticity, run model-locked vision triage with human review, dispatch scarce assessors by eligibility and ETA, join hazard exposure, and retain explainable evidence through settlement and appeal.

Operating contract

Make ownership visible before code.

Prove one bounded contract, identity handoff, failure response, and observable first success.

Application state: stateless
Planning calls: 0
Credentials accepted: No
Write authority: None

Capability map

entitlement-dependentCapture & Feedbackhybrid directAI & Locationhybrid directWorkmatestateful directGIS & Analyticshybrid directRoutes & Navigationhybrid

Normalized operation coverage

An adjacent API is never substituted when the captured corpus has no exact contract.

Capture & Feedback0 exact · reference onlyNo exact normalized REST operation is present in the captured contract corpus for this product. Use its source guides, SDK/widget/distribution surface, and entitlement process without substituting an adjacent API.AI & Location21 exact · normalized contractsExact normalized operations are linked below; account contract and entitlement still require validation.Workmate13 exact · normalized contractsExact normalized operations are linked below; account contract and entitlement still require validation.GIS & Analytics0 exact · reference onlyNo exact normalized REST operation is present in the captured contract corpus for this product. Use its source guides, SDK/widget/distribution surface, and entitlement process without substituting an adjacent API.Routes & Navigation11 exact · normalized contractsExact normalized operations are linked below; account contract and entitlement still require validation.

Claims system

Record consented incident location

Owns policy, claimant, incident declaration, coverage, reserves, decisions, settlement and appeal.

Supporting operation

Claim ↔ declared incident place and policy coverage snapshot

GETReturns the details of provided model/models/{api_model_key}This is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Evidence to retain

Record stage 1 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillMedia upload partially succeeds

Use per-object hashes and a submission manifest; keep the claim incomplete until all required evidence commits.

Consented capture and vision boundary

Capture guided photo evidence

Collects guided media, device/location accuracy, timestamps, hashes, capture policy and disclosure; an entitled SkyDNN adapter locks model identity, validates bounded derived geometry and confidence, and never treats metadata or inference as proof by itself.

Supporting operation

Evidence submission ↔ immutable media hashes, consent, times, accuracy, device/source

GETRouting API/{REST_KEY}/{resources}/{profile}/{geopositions}This is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Evidence to retain

Record stage 2 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillVision result is uncertain or sensitive

Preserve model and input identities, route to an independent reviewer, and prohibit automatic settlement or fraud decisions.

Interactive contract lab

Edit once. Generate eight trusted-runtime implementations.

The recipe starts from the normalized GET /models/{api_model_key} contract. Execute six deterministic fixture outcomes before an issued account is involved.

Local request composerCode stays local · fixtures are explicit

Generated in eight languages

Environment-backed credentials

GEThttps://ai.mappls.com/models/vidteq-ods-9

Credential-free sandboxExecute this contract without a provider call

How fixtures work

Generated from your inputs

curl --request GET \
  --url 'https://ai.mappls.com/models/vidteq-ods-9' \
  --header "Accept: application/json" \
  --header "Authorization: Bearer ${MAPPLS_AI_TOKEN}"

Credential-safe by constructionSet MAPPLS_AI_TOKEN only in your trusted runtime. Code generation stays local. Sandbox execution sends only bounded fixture inputs to this developer platform and never reads a credential or calls Mappls.

Reliability contract

Break the journey before customers do.

These controls are required at this operating depth; deeper recipes add durable truth rather than merely more API calls.

Bound inputs and outputsAbortable timeoutRetry only safe readsTyped empty and denied statesSafe request correlationCredential and URL-log redaction

Definition of done

Valid, empty, invalid-input, authentication-denied, rate-limited, timed-out, and unavailable outcomes are distinguishable.

The accepted Mappls or provider identity is retained separately from display text and coordinates.

Credentials remain in the approved runtime and logs retain only safe request evidence.

The exact source contract, auth generation, host, entitlement, quota, and region are reviewed before live traffic.

Continue with canonical evidence

Contracts, tutorials, and journeys stay linked.

Contract set

GETReturns the details of provided model/models/{api_model_key}GETTo get the list of tasks and their details/tasksGETRouting API/{REST_KEY}/{resources}/{profile}/{geopositions}GETReturns the details of all the models/models

Progressive tutorials

AdvancedQualify an iOS Mappls release2 hr AdvancedQualify React Native native parity100 min

Maintained capstone

Grid Restoration Desk

Correlate an outage, govern independent switching approval, dispatch an assigned crew, preserve rework, and reconcile restoration from telemetry and customer-impact evidence.

Inspect 14 verified tests Download full application

Source-grounded, not authority-granting

This recipe composes source-derived contracts, application architecture, fixtures, and maintained learning evidence. It does not prove package availability, provider payload shape, account entitlement, regional behavior, production compatibility, or release approval.