Average Adjusters · GA Documentation · ERF Protocol
One GA session.
Every interest, structured.
You declare General Average. You need B/L, commercial invoice, insurance certificate, average bond or guarantee from each cargo interest. Today that means 200 emails returning 200 different PDF formats over 3 months. With Vraimony, you open one session — each party receives a link, submits their documents in the same structured format, and you see the state of every interest in one place.
Role-aware per interest
Cargo owner · Forwarder · Insurer · Broker
PASS / Declared / Unverified per document
No account for submitters
◎ We package documentation for review. We do not calculate GA contributions or replace the adjuster's role.
How it works — three steps
Open a session. Send links. Receive structured submissions.
Step 1
Open a GA session via API
POST one request with the GA reference, vessel name, and list of cargo interests. Each interest specifies the party role and required documents. You receive an adjuster token and a unique submission link per interest.
POST /v1/ga/request
{
"ga_reference": "GA-2025-0441",
"adjuster_name": "Average Adjusters Ltd",
"vessel_name": "MV Example Vessel",
"interests": [
{ "role": "forwarder", "bl_ref": "BL-001",
"required_artifacts": ["bill_of_lading","commercial_invoice"] },
{ "role": "insurer",
"required_artifacts": ["average_guarantee","insurance_certificate"] }
]
}
Step 2
Each party receives a link — no account needed
You forward each submission link to the relevant party — forwarder, cargo owner, insurer, or broker. They open the link, see exactly what is required from them based on their role, and submit their document declarations. No Vraimony account needed.
✓ Cargo owner: Average Bond + B/L
✓ Forwarder: B/L + Commercial Invoice
✓ Insurer: Average Guarantee + Certificate
✓ Broker: Average Guarantee
Step 3
Check status — see what is missing
Your adjuster status URL shows the current state of every interest: submitted, pending, or exception. Each submitted document is labelled PASS, Declared, or Unverified. You see exactly what is still missing before you follow up — no inbox archaeology.
submitted
All required documents received
pending
Link sent — not yet submitted
exception
Party flagged a problem
Role-aware documentation model
Each party sees only what they need to provide.
GA documentation involves multiple parties with different obligations. Vraimony's interest model assigns each party a role — the submission form adapts to show the correct required artifacts for that role. No generic "upload anything" forms.
cargo_owner
Average Bond + Bill of Lading
Cash deposit if uninsured
forwarder
Bill of Lading + Commercial Invoice
Can act on behalf of cargo owner
insurer
Average Guarantee + Insurance Certificate
Pending insurer path if delayed
broker
Average Guarantee
Can chain to insurer confirmation
Required artifacts can be customised per interest. Defaults are based on standard York-Antwerp Rules documentation requirements.
What the adjuster sees — status response
One endpoint. Complete picture of every interest.
GET /v1/ga/status/GA-2025-0441 + Authorization: Bearer adjuster_token
// Verify a signed event from a forwarder/insurer submission
POST /v1/ga/verify-event
{ "event_type": "ga.interest.submitted", "ga_reference": "GA-2025-0441",
"timestamp_ms": 1748000000000, "signature": "sha256=abc123...",
"data": { "state": "submitted", "artifacts_count": 2 } }
// → { "ok": true } or { "ok": false, "reason": "invalid_signature" }
{
"ga_reference": "GA-2025-0441",
"completion_pct": 68,
"counts": { "total": 25, "submitted": 17, "pending": 6, "exception": 2 },
"interests": [
{
"interest_id": "GA-2025-0441-001",
"role": "forwarder",
"bl_ref": "BL-2025-0441-001",
"state": "submitted",
"artifacts": [
{ "type": "bill_of_lading", "status": "uploaded", "evidence_degree": 9 },
{ "type": "commercial_invoice", "status": "declared", "evidence_degree": 7 }
]
},
{ "interest_id": "GA-2025-0441-002", "state": "pending", "missing_artifacts": ["average_bond"] }
]
}
What Vraimony does and does not do
Documentation infrastructure. Not adjuster replacement.
✓ Sends structured requests to all parties simultaneously
✓ Labels each document PASS / Declared / Unverified
✓ Shows exactly what is missing from each interest
✓ Handles exception cases (uninsured, pending insurer)
✕ Does not calculate GA contributions or apportionments
✕ Does not replace average adjuster judgement
✕ Does not verify document authenticity — labels are declaration-based
✕ Does not store original documents — declarations only in Phase 1
Reviewer state — what the other side did
Know when the reviewer opened the link, acknowledged, or requested changes.
Every review link generates a reviewer state record. Use your certificate_token (from the seal response) to check what the reviewer has done — without exposing the sealed record itself.
POST /v1/review/open
Review surface (automatic)
Records first + repeat opens. No auth needed.
POST /v1/review/ack
Reviewer (ACK button)
Records acknowledgement + optional note. Idempotent.
POST /v1/review/mer
Reviewer (MER button)
Records amendment request + content. Multiple allowed.
GET /v1/review/state?id= + Authorization: Bearer
Sender (authenticated)
Returns full state: opened/ack/mer/declined + history.
pending
Link created — not yet opened
opened
Reviewer accessed the link
acknowledged
Reviewer sent ACK
mer_requested
Reviewer requested amendment
Managing a GA event?
Request a free pilot — 10 interests.
We run the first 10 cargo interests at zero cost. You tell us what works and what does not. If it saves you time — we talk about next steps.
Not legal advice. We do not calculate contributions or guarantee cargo release.