Alpha Covenant Holdings · partner integration · one page · 2026-10-03
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.
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.
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.
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.
POST https://alphacovenantholdings.com/api/batch?recurring=monthly&label=vendors-2026-10 (body: CSV; columns name, uei, npi, ccn, ein, state, reference)
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}/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. Expect roughly 8-12 receipts per minute; a 20,000-row file takes about 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.
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.
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.
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.
The single free receipt and the 25-row trial stay free. Partner 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.
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