reperix
Italiano Request a demo

Feature

You are not the one asking: your process is

Reperix is not only a chat to open. Your systems can ask on their own, at the moment it matters, and act on the answer: a workflow that routes, an app that pre-fills, a script that checks.

Why it matters

The moment you need the answer is inside the work, not after it

Useful information almost always arrives late: when somebody remembers to go looking. An invoice gets approved because nobody reread the contract; a case starts without anyone knowing the same customer wrote in about this two years ago. With the query API the process asks, automatically, at the exact point where the answer changes something.

  • The question comes from the process

    A workflow, a script, your line-of-business app: any system can ask Reperix a question and use the answer to decide the next step, with nobody opening a browser.

  • Each key sees only what you allow

    When you create an endpoint you choose which documents it answers over. Whoever holds the key cannot widen that perimeter, not even by asking about something else.

  • Answers come with their sources

    Alongside the answer you get the documents it was drawn from, with links to open them. The process can attach them, file them, or show them to whoever signs off.

How it works

Three steps, and the hard part is already done

  1. 1

    Create the key

    From the app: a name ("Invoice workflow"), the documents it may answer over, a daily call limit and, if you want, an expiry. You get a secret key.

  2. 2

    Call Reperix from your process

    Your system sends the question in plain language, the way a person would write it. It is a single call, the most common one there is: any software can make it, and in products with visual workflows it is often just a step to configure.

  3. 3

    Use the answer

    Back comes text with its sources cited. The process does what it likes with it: write it into a field, decide a route, open a task for a person.

It is the webhook in the other direction: that one brings documents into Reperix, this one sends answers out to your systems.

Examples

What companies do with it

  • Invoices worth a second look

    When an invoice arrives the workflow asks whether its terms match the supplier contract. If something is off, it goes to a human instead of straight to payment.

  • Cases to prepare

    Your app asks what the archive already says about this customer, and shows the summary to the operator before they open the case.

  • Replies to draft

    A request comes in by email: the system asks Reperix what the signed terms say and drafts a reply, with references to the documents.

Security

A key is not a master key

Every endpoint is born with a perimeter an administrator set: it answers only over those departments' documents, and the key cannot widen it. It has a daily call limit, it switches off in one click without touching your other integrations, and it can expire on a date you choose. No key opens the whole archive simply by existing.

For whoever integrates it

One call, no libraries to install

If you are reading this on behalf of the people who will wire it up, the question you care about is how much of their time it costs. This much: 

POST https://app.reperix.io/api/ask
Authorization: Bearer <your key>

{ "Question": "When does the Rialto contract expire?" }

The reply comes back as JSON: the text, and the list of cited documents with links to open them in the system they came from.

Got a process that would benefit?

Tell us where the question comes up today: in a demo we wire Reperix into that point and watch the answer arrive on its own.

Book a demo All integrations