Alpha Covenant Holdings · partner integration · one page · 2026-11-22

What you send, what you get back, how anyone verifies it, how billing works

The one question this answers: when your customer's auditor asks how the screen was performed, you hand them a receipt — the dated read of each official file, the key or exact name used, the SHA-256, and a Bitcoin-anchored proof that the receipt existed by that date. Nothing in it is a score, a risk label or an identity determination.

1. Authenticate

Header X-Api-Key: acv_…. Keys are issued per organisation, stored here only as a hash, revocable in one call (active:false). A 25-row trial key is self-serve at https://alphacovenantholdings.com/roster.

2. One receipt, now

POST https://alphacovenantholdings.com/api/batch/receipt
{"name": "Wellpath LLC", "uei": "", "npi": "", "ein": "", "ccn": "", "state": "", "partner_reference": "vendor-0412"}
→ 201 {"receipt_id", "sha256", "receipt_url", "proof_url", "partner_reference", "read_for", "read_by": "Alpha Covenant Holdings", "did_not_answer": [...], "not_read": [...], "receipt": {…full receipt…}}

Keys beat names: a UEI or NPI makes the match exact; a bare name returns exact printed-name rows as candidates for your reviewer. Up to 150 s while the sources answer.

2b. Payment-time read (accounts payable / treasury)

POST https://alphacovenantholdings.com/api/batch/receipt
{"name": "Wellpath LLC", "uei": "…", "partner_reference": "wire-2026-10-03-0412", "since": "r_<previous receipt_id for this vendor>"}
→ 201 {…, "since": {"receipt_id", "checked_at", "changes": [{"field": "sam.count", "old": 0, "new": 1, "source": "SAM.gov Exclusions…"}], "rows_now_for_changed_sources": {"sam": {"entries": […]}}, "reads_as": "1 line differs…"}}

Call it from the AP run before funds release. The response is the fresh receipt plus every line that differs from the previous read of the same party — a new exclusion row, a sanctions entry, a source that stopped answering — with the file dates. The hold rule is yours (for example: hold if any *.count rose on sam, leie, ofac, state, csl or uflpa); the receipt is the dated record of why the rule fired or did not. Duty Sheet: ap-pre-disbursement. Works the same from SAP Ariba, Coupa, Tipalti or a nightly script — it is one HTTPS call with a key.

3. A whole file

POST https://alphacovenantholdings.com/api/batch?recurring=monthly&label=vendors-2026-10   (body: CSV; columns name, uei, npi, ccn, ein, state, reference, forms = comma-separated form ids from /api/public-record/forms, printed on the row's receipt)
GET  https://alphacovenantholdings.com/api/batch/{batch_id}                → status, progress, counts, cycle_trigger, licenses_expiring_within_90_days
GET  https://alphacovenantholdings.com/api/batch/{batch_id}/coverage       → Coverage Ledger: rows with a dated record / none held / source silent, first and last read, laid against the receipt steps of the forms named (?forms= or the rows' forms column). Counts and dates only.
GET  https://alphacovenantholdings.com/api/batch/{batch_id}/results.csv    → one row per name: status, receipt_id, sha256, receipt_url, did_not_answer, changed_lines, license_expires, license_expires_in_days, cycle_trigger

Receipts are built a few at a time so that no upstream source is overrun. SAM.gov entity lookups by UEI are quota-limited by GSA; when a source does not answer, the row is marked partial and retried the next day rather than printed as clear. Measured 2026-10-11: 100 names in 5 minutes (about 20 receipts per minute) when every source answered; expect 8-20 per minute, so a 20,000-row file takes between one and two days end to end. Recurring batches re-run every 30 days and within the hour whenever a held source file changes (LEIE, SAM extract, any state list) — the result says which file changed and the date the source printed on it. Public log.

3b. Webhook push

Add ?webhook_url=https://… when you create a roster (or webhook_url on a Receipt Watch) and we POST the dated summary to that URL when each cycle completes — including the cycles we start within the hour an official file changes. The body carries the counts, the line-by-line changes and the results URL, with an X-Alpha-Covenant-Sha256 header over the body. It is a push of what the files printed, not an alert that anyone "hit" anything; the rule that acts on it is yours. HTTPS only; failures are logged on the batch, not retried into a flood.

Every body also carries events[], one ENTITY_STATE_DELTA per changed line, so an ERP or GRC system can consume line items without parsing the summary:

{"event": "ENTITY_STATE_DELTA", "timestamp": "2026-10-03T23:17:59+00:00",
 "entity_keys": {"name_as_supplied": "Example Corp", "cage": "7X1A2", "ein": "12-3456789"},
 "delta": {"source": "uflpa", "source_as_printed": "UFLPA Entity List (FLETF, 19 U.S.C. 4681) — …", "action": "ROWS_UNDER_PRINTED_NAME_CHANGED",
           "field": "uflpa.count", "previous": 0, "now": 1, "match_method": "exact printed name …",
           "file": {"fetched_at": "…", "file_sha256": "…", "source_last_modified": "2026-10-03"}, "rows_now": [ … the row as the notice prints it … ]},
 "receipt_id": "…", "receipt_sha256": "…", "previous_receipt_id": "…",
 "reads_as": "What the official file printed on each of the two dates. Whether to act is your rule; …"}

Actions are ROWS_UNDER_PRINTED_NAME_CHANGED, SOURCE_STATE_CHANGED (answered ↔ did not answer), DISCLOSURE_LIST_CHANGED, SAM_RQ_RECORD_POSTED / SAM_RQ_RECORD_COUNT_CHANGED (a Responsibility/Qualification record an agency entered in SAM for the UEI), SAM_REGISTRATION_CHANGED (status, expiry or purpose as SAM prints them), SAM_SELF_CERTIFICATION_CHANGED and WARN_NOTICE_POSTED / WARN_NOTICE_COUNT_CHANGED. The event never says an entity "was added to" a list: the UFLPA, 1260H, CSL and most exclusion files carry no CAGE, EIN or UEI, so a new row is a printed-name match beside the keys you supplied — the identity question stays yours. The same events[] comes back on a payment-time read (since=).

4. What a receipt contains

For every source: name, file date or read time, the exact query, the rows returned verbatim, and did_not_answer / not_read states that are never silently blank. The receipt's sha256 is the hash of its canonical JSON. Schema and conformance: https://alphacovenantholdings.com/api/receipts/spec.

5. How anyone verifies it — without trusting us or you

GET https://alphacovenantholdings.com/api/receipts/{receipt_id}                                 → the receipt as recorded
POST https://alphacovenantholdings.com/api/receipts/{receipt_id}/verify                         → recomputes the hash
GET https://alphacovenantholdings.com/api/public-record/archive-hash/prove/{sha256}             → the UTC day whose archive includes this hash, its members list, and the .ots proof
ots verify  (any OpenTimestamps client)                                → Bitcoin block attestation of that day's digest

Daily self-check of our own receipts, in public: https://alphacovenantholdings.com/audit.

6. Co-branding rule

Your name and logo may appear on the receipt page as read for. Read by Alpha Covenant Holdings stays visible, and the content is byte-identical to the free receipt. A white-label that hides the reader would break the custody chain your auditor is relying on, so we do not offer one.

7. Billing — and what it never touches

The single free receipt and the 25-row trial stay free. Self-serve by card at https://alphacovenantholdings.com/partners: Basic $99/month (5,000 single receipts — section 2 and 2b) or Monitor $499/month (50,000 calls, rosters and watches included); the key is issued at checkout and works on every endpoint on this page. Enterprise agreements are annual: a platform fee plus volume receipts, with a monthly row limit printed on the key. Billing never changes what a source returned, which sources are read, how often, or what the receipt says. Public-record evidence, not legal advice, not a compliance determination, not an identity match.

7b. Audit Handover licence

GET https://alphacovenantholdings.com/api/partner/v1/handover/{UEI} (X-Api-Key) returns the Audit Handover file — five years of one organization's Single Audits as filed, findings threaded across years, the organization's corrective-action text, the next 2 CFR 200.512 date by rule — for display inside your product. Licence terms: Read by Alpha Covenant Holdings stays visible wherever the file is shown and your brand prints as issued_via; nothing in the filing's text is altered; no conclusion about the organization is added under our name. Metered per customer per calendar month ($36, $720 minimum in a month with reads; GET https://alphacovenantholdings.com/api/partner/v1/handover shows the month as it will be invoiced) or by revenue-share agreement (20% of your price, same floor). Displaying, caching or redistributing the file or the public page's content inside a product without this licence is outside the Acceptable Use Policy at https://alphacovenantholdings.com/legal/acceptable-use.

8. What we do not do

No scores, no risk labels, no PEP or adverse-media screening, no beneficial-ownership inference, no fuzzy matching presented as a match, no access-restricted files (DMF, CMS Preclusion, DEA registrant file, BOI) presented as read. Everything not read is named: Known Limits.

Contact: chris@edmondsholding.com · https://alphacovenantholdings.com