Arakma
Every uncertain field checked by a person

Turn any document into structured data

Invoices, forms, statements, contracts, IDs — scanned, photographed or born digital. Arakma reads the fields you define, scores every one, and routes anything it is not sure about to a person before it reaches your system.

On your own documents · billed per page · stored encrypted in the EU

Accepts
  • PDF
  • JPG
  • PNG
  • TIFF
  • DOCX
  • scans
  • phone photos

Arabic, French and English — including two on one page

What you get

Built for the documents that break everything else

Any model can read a clean page. The work is the one that is skewed, stamped, half handwritten, or missing the field you needed.

Any layout, any condition

Scans, phone photos, exports, born-digital PDFs. Rotated, stamped, multi-column, two languages on one page. The messy ones are the reason this exists.

Your fields, your names

You define the schema once. Every response comes back with exactly those keys, typed and in that shape — not a bag of whatever happened to be on the page.

A score on every field

Calibrated per field, not per document, so one hard field does not drag a whole page down. You set the line — 85% by default — that decides what can go through untouched.

A person on the exceptions

Anything under the line is checked by a reviewer with the document open beside the field. The correction is logged against the job, and it is how the system gets better.

The mechanism

The score decides the route

Nothing uncertain is quietly guessed at, and nothing uncertain reaches you unchecked. You move the line; 85% is where it starts.

0.85review queuefieldsyour system0.990.970.940.980.681.00

At or above the line

Delivered straight through. Nobody on your team sees it, because there was nothing for them to decide.

Below the line

Held back and shown to a reviewer with the document open beside the field, then corrected before anything is sent.

Either way

One webhook, one payload shape, and every correction logged against the job with the actor and the timestamp.

The integration

Two calls, and you are done

Name the fields in a sentence or point at a saved schema. Post the file, get a job id back immediately, and collect the finished result on your webhook — after review, if review was needed.

Send a documentPOST
curl https://api.arakma.com/v1/extractions \
-H "Authorization: Bearer $ARAKMA_KEY" \
-F "file=@invoice_8842.pdf" \
-F "prompt=invoice number, issue date, vendor, total" \
-F "webhook=https://yourapp.com/hooks/arakma"
 
# Returns a job id immediately. Nothing blocks on the extraction.
Collect the resultwebhook
{
"jobId": "job_01HQ8F2",
"status": "done",
"fields": [
{ "key": "total_amount",
"label": "Total amount",
"value": "12460.00",
"confidence": 1.0,
"page": 1 }
]
}

Document types

There is no list to pick from

The schema is the product, not the document type. Describe the fields you need in plain language, or save a schema and reuse it — the same extraction and the same review step apply either way.

These are the shapes it is built around. If yours is not here, that does not make it a special case — bring one and we will show you the output before you pay anything.

  • Invoices
  • Purchase orders
  • Receipts and expenses
  • Bank statements
  • Contracts
  • Delivery notes
  • Application forms
  • Identity documents
  • Insurance claims
  • Remittance advice
  • Utility bills
  • Shipping documents
  • + whatever you describe

By industry

Where teams use it

The same schema and review step, set up around the documents and the checks each trade already runs.

Handling

The procurement questions, answered up front

Your region, not ours

Chosen per tenant when the account is created. Documents are stored encrypted in that region and are not copied out of it.

Never training data

Your documents are not used to train any model, ours or a vendor's. The processing agreement with our model provider prohibits it.

Gone when you say

Thirty days by default, or whatever you set. The file and its extracted values are deleted together, and you can delete a job sooner by API.

Try it on your own documents

Tell us which documents you handle and we open an account for your team. Upload a PDF or a photo, say what you need out of it, and see exactly what comes back — including which fields we would not trust without a person checking them.

We reply within one business day.