Pagination

Partner operating systems should use Partner Read under /api/v1 (contractVersion: arbiter.partner.v1). List responses are versioned envelopes — not bare arrays.

Partner list envelope

{
  "contractVersion": "arbiter.partner.v1",
  "orgId": "…",
  "generatedAt": "2026-07-21T00:00:00.000Z",
  "snapshotId": "snap-…",
  "evidence_hash": "…",
  "verified_no_npi": true,
  "pagination": { "limit": 50, "count": 50, "nextCursor": null },
  "items": []
}

Field	Meaning
`evidence_hash`	Fingerprint of the envelope contents for independent verification
`verified_no_npi`	Envelope is metadata-only — policy bodies and NPI are not included
`snapshotId`	Optional consistency marker for coverage / proof reads
`pagination.nextCursor`	Opaque cursor for the next page; `null` when finished

Cursor pagination

curl -H "Authorization: Bearer $ARBITER_API_KEY" \
  "https://arbiter.blockskunk.com/api/v1/assets?limit=50"

# subsequent page
curl -H "Authorization: Bearer $ARBITER_API_KEY" \
  "https://arbiter.blockskunk.com/api/v1/assets?limit=50&cursor=$NEXT_CURSOR"

Unversioned UI list paths remain for the dashboard; partners must not treat them as a stable contract. Full endpoint catalog: API reference.

Next: Webhooks