Skip to the operations

Compliance

Inscribe in a decision flow.

5 Inscribe operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Compliance
Type
Integration
Authentication
API key
Test environment
Production host only

Who they are

Detects altered paystubs, bank statements and IDs.

Inscribe reads documents uploaded during an application and reports whether they were edited: inconsistent fonts, tampered PDF metadata, figures that do not reconcile, or a template it has seen used before. It exists because an altered paystub is one of the cheapest frauds to commit and one of the hardest to catch by eye.

What a flow can call

5 operations, each one a step you can place on the canvas.

  1. POST/api/v2/customers

    Create a customer

    Everything in Inscribe hangs off a customer, so this comes first — the documents and the fraud verdict attach to the id it returns.

  2. GET/api/v2/customers/$data.inscribe_customer_id/documents/$data.inscribe_document_id

    Get a document's fraud verdict

    The call a decision actually branches on. trust_score runs 0 to 100 and risk_assessment.insights lists the individual fraud signals with a rationale — which is what an adverse action file needs, rather than the bare score.

  3. GET/api/v2/customers/$data.inscribe_customer_id/documents

    List a customer's documents

    Every document on the customer with its state and scores.

  4. GET/api/v2/customers/$data.inscribe_customer_id

    Get a customer's risk assessment

    The customer-level view: the risk assessment rolled up across every document, plus the canonical profile Inscribe derived from them.

  5. GET/api/v2/customers

    List customers

    Customers on the account, newest first. Cheapest way to confirm a token works before wiring anything else.

Where it sits in the decision

Compliance calls have a natural place in a flow.

Screening answers the parts of a decision a regulator will ask about, so what matters is not only the verdict but the record of it. A partial match is the interesting case: rarely a decline on its own, and usually the point where the flow opens a case for a reviewer with the match evidence attached.

Whatever Inscribe returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Inscribe as a connection authenticating with an API key.
  • 02Inscribe has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Create a customer” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Inscribe in a flow.

How do I connect Inscribe to a decision flow?

Add Inscribe as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Inscribe in a decision without ever seeing the secret.

Can I test Inscribe without touching production?

Inscribe exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on Inscribe?

5 operations, including “Create a customer”, “Get a document's fraud verdict”, “List a customer's documents”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Create a customer”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Inscribe be called?

Screening answers the parts of a decision a regulator will ask about, so what matters is not only the verdict but the record of it. A partial match is the interesting case: rarely a decline on its own, and usually the point where the flow opens a case for a reviewer with the match evidence attached.

Also in Compliance

Ready when you are

Wire Inscribe into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs