Partner integration

Put independent GPU technical assurance inside your underwriting workflow.

Partners can initiate a Doku review through the portal or API, receive normalized status updates, surface conditions inside their own workflow, and provide investors with a separately signed Doku technical opinion designed to support their review of the financed technical case.

Partner sign in Request partner credentials Open the API sandbox Run the evidence pack Download OpenAPI

Integration principles

Embed the workflow, not the independence.

Approved presentation: Independent Technical Review by Doku Assurance

Operationally embedded

Visibly independent

Partner retains origination and credit ownership

Doku retains control of technical scope and opinion

Borrower evidence remains source-linked

No fully white-labeled technical opinion

Shared review lifecycle

One normalized path across all three products.

1Partner intake
2Conflict and scope review
3Evidence request
4Technical review
5Independent opinion
6Financing decision
7Condition closure
8Optional post-close assurance

Trigger rules

Call Doku when the decision needs a separate technical record.

First-time operatorUnusual cluster or cloud architectureMaterial exposureIncomplete evidenceInvestor or syndicate requestClosing or draw milestonePerformance acceptance pendingRepeated SLA or availability issues

Cross-product contract

Product-specific deliverables. Shared status and controls.

Product 01

Independent Second Opinion

Independent technical opinion, challenged assumptions, structured evidence, and financing conditions

View product

Product 02

Full Technical Underwriting

End-to-end evidence review, selected technical testing, acceptance requirements, and credit translation

View product

Product 03

Acceptance & Draw-Condition Review

Condition-closure verification, exceptions, and draw-readiness opinion

View product

Runnable evidence model

Follow 256 installed GPUs to 192 supported contracted capacity.

A runnable, deterministic demonstration of how Doku links a submitted GPU plan, protected power, technical qualification, contract acceptance, and an illustrative cash-flow bridge without turning missing evidence into a pass.

All transaction facts and financial inputs are invented. This is not a customer case, credit decision, technical opinion, covenant calculation, or proof of real-world performance.

Open the synthetic evidence pack Verification summary

Installed: 25632 homogeneous eight-GPU nodes
Power-admissible: 22428 full-system envelopes after ancillary reservation
Technically qualified: 208One failed and one missing health result excluded
Contract-eligible: 192Three complete, accepted 64-GPU pools

Partner API

Small surface. Explicit controls.

Test and live credentials are separate, hashed at rest, scoped, rotatable, revocable, and partner-rate-limited. Use a unique idempotency key for creation. Webhooks use timestamped HMAC-SHA256 signatures with replay rejection and bounded retries.

GET   /api/v1/products
GET   /api/v1/reviews
POST  /api/v1/reviews
GET   /api/v1/reviews/{reviewId}
PATCH /api/v1/reviews/{reviewId}
POST  /api/v1/reviews/{reviewId}/materials
GET   /api/v1/reviews/{reviewId}/deliverables
POST  /api/v1/reviews/{reviewId}/deliverables/{deliverableId}/signed-download
GET   /api/v1/reviews/{reviewId}/audit
POST  /api/v1/reviews/{reviewId}/conditions
GET   /api/v1/reviews/{reviewId}/conditions

View OpenAPI JSON Download integration brief Example request

Separate review states

Workflowpreflight_requestedconflict_checkscope_pendingawaiting_materialsunder_reviewdeliverable_readyclosedcancelledTechnical conclusionsupportablesupportable_with_conditionsinsufficient_evidencenot_supportable_on_current_evidence

Partner readiness

Controlled onboarding from sandbox to live.

Onboarding and timeline

Fit and operating-model review
Contracting, confidentiality, permitted-use, and data-processing terms
Security and webhook review
Sandbox credential and integration test
Live-credential approval and controlled launch

Integration timing is confirmed after fit and security review. No public production keys are issued.

Versioning and deprecation

Clients send the documented schema version. Compatible additions remain within the version. Breaking changes use a new version with a communicated migration window and deprecation date.

Custom partner-volume pricing is separately scoped and is not a public rate card.

Security and data processing

Private records use access-controlled persistence. Evidence URLs are treated as secrets, never fetched automatically, and excluded from analytics and routine notifications. Status access uses signed exchange links and short-lived cookies.

Current workflow providers may include Vercel for hosting and private object storage, and Resend for transactional delivery where configured. Final subprocessor, retention, deletion, and data-processing terms are confirmed in contracting.

Support, escalation, and incidents

Operational support and escalation begin at jorg@dokuassurance.com. Security or privacy incidents should use the same address with “Security incident” in the subject. Contracted response targets supersede public guidance.

Responsibility matrix

Workflow ownership remains explicit.

Activity	Partner	Doku	Borrower or operator	Lender
Origination and permitted disclosure	Responsible	Conflict review	Provides authorized information	Accountable
Technical scope and opinion	Consulted	Responsible and accountable	Provides evidence and access	Consulted
Credit, waiver, and draw decision	Workflow support	Technical input only	Informed	Responsible and accountable
Incident and deletion request	Notifies	Coordinates within scope	Supports facts	Informed

Co-branded operating model

Partner platform

Doku conflict and scope review

Evidence and selected testing

Doku technical opinion

Partner credit workflow

Condition closure

Optional post-close assurance

The workflow may be embedded. The technical opinion remains independently Doku-branded and signed.

Partner credential request

Begin with fit, security, and operating-model review.

Doku does not issue public production API keys through the sandbox. Submit business contact information to begin a controlled credential and webhook configuration process.