Integration prompt

A better brief.
A stronger integration.

A focused integration brief grounded in the Amlok contract, your environment and production-ready handling.

Amlok / CONNECTED INTELLIGENCE

EvidenceContextHuman judgment

COPYABLE DEVELOPER BRIEF

Give your agent the context.

Adapt this guide to your environment and workflow. It contains instructions and references, not credentials or an API client.

integration-brief.txt

Build an Amlok integration for our institution’s approved workflow.

Start with https://docs.amlok.io/llms.txt and the OpenAPI contract at https://docs.amlok.io/openapi/amlok-v1.json. Read the quickstart, product scope, integration security, and relevant sandbox journey before implementing endpoints. Use the current contract for exact operation names and schemas.

Ask the developer to provide the framework, intended Insights or Signal journey, workspace scope, and institution-issued sandbox base URL. Read API credentials from the server environment; never put secrets in client code, logs, prompts, or source control.

Implement input validation, workspace authorization, explicit asynchronous states, safe retries, and error handling. Verify webhook signatures against raw bytes; persist accepted events and deduplicate deliveries before processing. Retrieve authoritative results and their source evidence.

Keep approval, borrower outreach, payments, and consequential interventions in institution-owned systems. Do not invent API endpoints or convert missing evidence into a valid zero.

Validate against the provisioned sandbox, including expired access, incomplete evidence, repeated requests, duplicate events, and unavailable providers. Summarize tested behavior and remaining deployment requirements for engineering review.

Keep secrets and borrower information outside your instructions.

Download integration brief

Provide the source of truth

Ask your agent to read the current OpenAPI contract and relevant product journey before writing code. Supply your framework and intended workflow without sharing live credentials.

Make the behavior concrete

Include scope checks, asynchronous state handling, idempotent retries, signed webhooks and evidence retrieval. Request tests for missing permission, expired authorization and duplicate delivery.

Review before enabling live data

Have an engineer verify the generated integration against the provisioned sandbox, permissions and business requirements. Keep decisions and consequential actions under your institution’s control.

BUILD WITH THE RIGHT REFERENCES