Skip to main content

For certifiers and auditors: read the records, not a folder of files.

Sign the certificates you issue, withdraw them when you must, read the evidence of the lots a company gives you access to, and verify a signed report without an account.

Glassware on a laboratory bench

What you record

  • The certificates you issue

    Uploaded for the lots that concern you. A certificate signed by its issuer carries the highest evidence level.

  • Withdrawals

    Only the issuer withdraws a certificate. A company that disagrees marks it disputed, with a reason and the evidence, and you are told; it still counts until you withdraw it.

  • Lab results

    On the lot they describe, with the lab that issued them.

What you approve

  • Nothing in the company's records

    With verifier access you read; you never change a company's records. The company's people approve every change.

  • The access you are given

    Chosen lots for at most one year, created by the company's owner with a second factor, with every read logged.

  • Reading by software

    With the credential you receive, your software or AI agent reads through the API or the MCP server, and sees only the lots and the evidence the access covers.

  • Whether you are trusted

    Each company chooses the issuers it trusts for each type. A certificate from an issuer it no longer trusts says so.

What you prove

  • What is signed and what is only declared

    Every certificate shows its evidence level: declared by the company, recorded for a party, or signed by the party itself.

  • The certification audit pack

    Certificate validity and certified volume reconciliation, signed.

  • Any report, checked without an account

    The verification page checks a signed copy. It does not need an account or trust in A-REX.

See it from the auditor's side.

Tell us what you certify or audit. We will show what a company can give you access to, and how you check a report.