ProbaFide

Proof rails for AI agents.

Verification, evidence receipts, and notarial handoff for workflows that require legal authority.

ProbaFide is an MCP-first verification and notarial-handoff layer for AI agents working in legal, financial, corporate, real-estate, and diligence workflows.

Contact For developers

Evidence receipt

rec_01JZB7H4M3
source-bound 
{
  "ok": true,
  "source": "brasilapi",
  "legal_assurance_level":
    "public_api_observation",
  "receipt_id": "rec_...",
  "request_sha256": "9f7a...",
  "response_sha256": "61c4..."
}

What it is

Agent-native verification with explicit limits.

What ProbaFide does

ProbaFide gives AI agents a safe way to verify legal-adjacent facts, create audit receipts, and escalate to authorized notarial channels.

It provides structured verification tools, source-bound outputs, evidence receipts, and human notarial handoff packets for workflows where the agent must separate observed facts from legal authority.

What ProbaFide is not

  • Not a cartório or tabelião.
  • Not an official government service.
  • Not legal advice.
  • Not a replacement for lawyers, e-Notariado, or signature platforms.

ProbaFide is not a cartório, notary, legal authority, government service, or substitute for legal advice.

Trust ladder

Observed is not the same as notarized.

ProbaFide separates evidence, technical checks, and authorized human acts so agents know when to stop and escalate.

Observation01

Data returned by a public or official source.

A source-bound observation can answer what was seen, when, and from where.

Evidence02

Observation plus timestamp, hash, and receipt.

The receipt makes the check auditable without turning it into legal authority.

Conformity check03

Technical validation of a file or signature.

A configured provider can return a signature-conformity report; otherwise ProbaFide fails closed.

Handoff04

Structured packet for human authority.

A handoff packet packages the facts, hashes, limitations, and requested review path.

Legal authority05

Completed act by an authorized entity.

This requires a partner-confirmed event from an authorized notarial rail.

observed ≠ verified ≠ validated ≠ notarized

How it works

From agent request to receipted boundary.

The product surface is built for agents first: deterministic tools, structured outputs, and a clear escalation decision.

01

Agent

Receives a counterparty, address, file, or workflow question.

02

MCP tool

Calls a narrow ProbaFide tool with explicit input.

03

Source-bound response

Returns what was checked, which source was used, and what came back.

04

Receipt

Records timestamp, source, hashes, assurance level, and limitations.

05

Escalation

Creates a handoff when human review or an authorized notarial act is required.

Product contract

Every answer resolves five questions.

  1. What was checked?
  2. What source was used?
  3. What did the source return?
  4. What is the assurance level?
  5. What receipt proves the check happened?

Assurance levels

Each result carries a plain-language boundary.

The assurance level states what ProbaFide can support from the source and what still requires review or authority.

public_api_observation Observed from a public or community API.
official_api_observation Observed from an official API.
signature_conformity_check Technical signature validation performed.
notary_handoff_pending Local or submitted handoff pending human or legal authority.
notarial_act_completed Completed by an authorized notarial partner or system; requires a partner-confirmed event.
unavailable Tool failed, source unavailable, or credentials missing.

For developers

MCP-first, fail-closed, receipt-native.

ProbaFide is designed as a narrow tool layer that agents can call before acting inside legal-adjacent workflows.

Brazil-first MVP — in development · early access

Unavailable credentials, disabled providers, and missing partner rails return structured limitations instead of optimistic conclusions.

br_cnpj_lookup br_cep_lookup validate_br_signature_file create_notarial_handoff get_receipt healthcheck
probafide stdio + json 
$ probafide cnpj 00000000000191 --json
{
  "ok": true,
  "source": "brasilapi",
  "legal_assurance_level": "public_api_observation",
  "receipt_id": "rec_..."
}

$ probafide mcp

Brazil first

Built around civil-law notarial tradition and digital rails.

Brazil is the first market because it combines a civil-law notarial tradition, digital notarial infrastructure, and public or official data rails. ProbaFide starts there and expands toward civil-law markets where agents need evidence, boundaries, and human-authority handoff.

Principles

Conservative by design.

01

Never fake authority

If credentials, sources, or partner rails are missing, return a structured limitation.

02

Every answer has a source

No source, no verification.

03

Every check has a receipt

No receipt, no auditability.

04

Every receipt has limitations

The receipt should say what it does not prove.

05

Agents should escalate

A good result can say human notarial review required.

06

Start with Brazil

Build for civil-law markets, with Brazil as the beachhead.