Integration catalogue
Choose a customer-owned cloud, regulated workflow or partner-neutral knowledge source without presenting potential channels as confirmed partnerships.
Open machine-readable catalogue →Enterprise integration kitConnect one workflow.
Connect one workflow.
Keep the boundary yours.
EcoKure sits around the AI, rules or evidence workflow you already operate. Your system sends a bounded decision request; EcoKure returns a verdict with an evidence contract. The customer owns the deployment boundary and decides what moves.
A declared integration seam
Bring the request. Carry the boundary.
Trace the contract between an existing system and a supported EcoKure method.
Select an illustrated object to inspect its role.
01 / 03
Name the actor, target and conditions.
An integration begins with a workload and an explicit request contract. Identify the required evidence and supported route.
Integration depends on the releaseConditions & scope
Inspect product availability ↗A conceptual connector is not an available production integration. Confirm support against the intended package and environment.
The connection
Build a pilot brief →
See it work →
Inspect evidence →
One small seam between your system and the evidence layer.
How a request travelsRequest in. Verdict out. Evidence retained.
Keep the workflow you already operate.
Your model, application or operator continues to propose the output. The integration sends only the fields needed for the selected Control Pack.
EcoKure does not replace the source system or take ownership of its data.Return a bounded verdict.
The Control Tower resolves the tenant-scoped rules, checks the evidence state and returns ALLOW, REVIEW, BLOCK or ABSTAIN with a reason.
Uncertainty becomes a review route rather than a guessed answer.Keep the contract with the result.
The response can be stored, reviewed and replayed in the customer-controlled boundary with its rule version, evidence identity and outcome.
Exact adapters and retention are validated during the pilot.Production boundary: this page documents the integration shape, not a claim that every adapter is already built. Start with one workflow and validate the exact payload, failure mode and retention position during the pilot.
Verification example
Use the same contract from a script, service or JARVI3.
A customer integration can verify its tenant-scoped credential before requesting work. The raw key is issued once by an authorised operator, stored as a hash by EcoKure and transferred through the customer’s secure channel.
curl -X POST "$ECOKURE_BASE_URL/api/access/verify" \ -H "X-API-Key: $CUSTOMER_API_KEY" \ -H "Content-Type: application/json" \ -d '{"scope":"access:verify"}'
access:verifytaxonomy:readevidence:writetenant-scopedKey safety: never put an admin key in a browser URL or frontend bundle. Production credentials belong in the customer’s secret manager, with expiry, rotation, revocation and offboarding recorded in the pilot agreement.
What the buyer receives
A usable handoff, not just an endpoint.
Evidence contract
Inspect a signed non-customer example and verify it offline before discussing production data.
Download demo EvidencePack →Tenant onboarding
An authorised operator creates the tenant, selects the mapping, issues a scoped key and records the initial readiness event.
Review readiness requirements →Customer workspace
Once SSO and membership are configured, reviewers see their own Control Packs, queue, changes and evidence without access to EcoKure’s shared corpus.
Open sign-in path →Downloadable contracts
Give your technical team the starting point.
The starter kit defines the API, Control Pack and EvidencePack shapes used to scope a bounded pilot. It is deliberately explicit about what still needs customer validation.
Start with one workflow.
Define the boundary, run in shadow mode, create the evidence and decide together whether the production path is justified.
Generate a pilot brief →