Proof-of-delivery sufficiency against a required evidence list

$0.005 USDC per call · Business, finance and compliance · POST /api/v1/pod-sufficiency · Id pod-sufficiency

Checks whether the proof-of-delivery evidence supplied (signature, photo, timestamp, GPS fix, recipient name, scan ...) satisfies the carrier or contract requirement list the caller gives: every required item, plus optional 'at least k of these' groups, with value bounds (for example GPS accuracy at most 30 m) and maximum age. For an agent assembling a delivery dispute or a payment release. Returns which items are present, missing or out of bounds; does not validate that a signature or photo is genuine, and absent evidence is unknown, not pass.

What you get

Stops a claim or release going out with a missing proof element, and names it.

Call it

Send the JSON body below to https://agents.writerslogic.com/api/v1/pod-sufficiency. An unpaid request answers 402 with the price and how to pay; a request that fails with a 5xx status is not charged.

curl -i -X POST https://agents.writerslogic.com/api/v1/pod-sufficiency \
  -H 'content-type: application/json' \
  -d '{"required":[{"key":"recipient_name"},{"key":"delivered_at","maxAgeDays":30},{"key":"gps_accuracy_m","max":30}],"anyOf":[{"id":"proof","keys":["signature","photo"]}],"evidence":[{"key":"recipient_name","value":"J. Rivera"},{"key":"delivered_at","value":"2026-10-30T14:02:00Z","asOf":"2026-10-30"},{"key":"gps_accuracy_m","value":12},{"key":"photo"}],"asOf":"2026-11-04"}'

Input

FieldTypeRequiredDescription
requiredarray<object>; max 100 itemsyesEvidence every proof must contain (key plus optional bounds).
anyOfarray<object>; max 20 itemsnoAlternative groups: at least atLeast (default 1) of the keys must be present.
evidencearray<object>; max 500 itemsyesProof elements the caller holds.
asOfstring; length 0..40noReference instant (ISO date or instant) for evidence age; required only when a need sets maxAgeDays. The check never reads the clock.

Example request body

{
  "required": [
    {
      "key": "recipient_name"
    },
    {
      "key": "delivered_at",
      "maxAgeDays": 30
    },
    {
      "key": "gps_accuracy_m",
      "max": 30
    }
  ],
  "anyOf": [
    {
      "id": "proof",
      "keys": [
        "signature",
        "photo"
      ]
    }
  ],
  "evidence": [
    {
      "key": "recipient_name",
      "value": "J. Rivera"
    },
    {
      "key": "delivered_at",
      "value": "2026-10-30T14:02:00Z",
      "asOf": "2026-10-30"
    },
    {
      "key": "gps_accuracy_m",
      "value": 12
    },
    {
      "key": "photo"
    }
  ],
  "asOf": "2026-11-04"
}

Result

The response is { "data": ..., "_provenance": ... }. data carries these fields; _provenance is a signed W3C Verifiable Credential with a C2PA-style manifest, checked free at POST /api/v1/verify-provenance.

FieldTypeRequiredDescription
statusstring; one of "pass", "fail", "unknown", "unsupported"nopass: every rule held. fail: a rule was violated (see witnesses). unknown: the input lacks the evidence to decide. unsupported: outside what this engine covers. Missing evidence is never a pass.
requirementsarray<object>no
countsobjectnoNon-optional requirements by state; optional ones are counted separately.
sufficientone ofnotrue when pass, false when fail, null when undecidable.
missingarray<string>; max 100 itemsnoKeys with no evidence.
outOfBoundsarray<string>; max 100 itemsnoKeys whose evidence violates the bound or value.
witnessesarray<object>no
versionsobjectnoEvery semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile).
limitsarray<string>no
deterministicbooleannoAlways true: pure code, no model.

Pay and connect

Available through: x402 (USDC on Base), MCP. MCP clients reach it through the compliance-evidence-kit package.

Machine-readable