Get the client.
Choose one action.
RuleEvo is the authority lifecycle and execution-evidence layer for autonomous agents. The JavaScript client is free to download and use for your RuleEvo integration. It has no dependencies and supports Node 22+ or a compatible fetch runtime. Live access currently requires an agreed, bounded integration and separately issued credentials.
Download the caller-side effect runner · Lifecycle quickstart with HTTP, Drive and sandbox examples · REST API reference
These downloads do not create a hosted account. Use the API reference against your agreed private deployment; the public marketing website is not an open execution endpoint.
Read before you write
Save the client as ruleevo.mjs beside a server-side script. Keep both your actor key and the private deployment's service access token in your own secure server environment. Never place these secrets in browser code, public repositories or a chat message.
import {RuleEvoClient} from './ruleevo.mjs';
const client = new RuleEvoClient({
baseUrl: process.env.RULEEVO_BASE_URL,
apiKey: process.env.RULEEVO_API_KEY,
serviceAccessToken: process.env.RULEEVO_SERVICE_TOKEN
});
// One read-only request. It does not authorize or execute work.
const snapshot = await client.tasks();
console.log('Assigned tasks:', snapshot.grants.length);Configure those variables for the agreed deployment, then run your script with Node. Importing the client alone does not call RuleEvo or execute work; the tasks() example makes one read-only request. Without valid deployment access and actor credentials, requests fail; downloading a client does not create a customer account.
Integrate the authority-to-effect lifecycle
Keep authorization, execution and outcome evidence distinct. A consequence-bearing write should follow this sequence in your controlled adapter:
- Delegate bounded authority. Specify the actor, operation, resource, budget and expiry; delegated permissions cannot widen the original authority.
- Admit an exact effect. Persist one stable identity and bind the intended payload digest, provider, resource and environment. Check current authority at the execution boundary.
- Execute externally. Claim dispatch once and let the trusted adapter call the provider. Admission alone is not proof of execution. Provider-side deduplication is still required where available.
- Report known or unknown. Distinguish completed work and a known failure from an uncertain result. Unknown is not failed; a lost acknowledgement must not cause a blind write retry.
- Reconcile. Read provider state before another attempt. Withdrawal blocks future admission, but previously admitted work may finish and completed effects stay completed. Compensation is a separate, newly authorized effect.
- Record evidence. Keep the admission snapshot and observed outcome together. A signed RuleEvo record authenticates RuleEvo assertions; it is not provider attestation or independent proof that a third party stopped.
The read-only example above remains the safe first connection check. The current downloadable client and agreed deployment define the endpoints available to your integration; do not infer live access or a completed effect from downloading code. This is not a general-purpose request proxy or an orchestration engine.
Starter access
Starter software access is $10/month including 10,000 unique authorized prechecks, then $0.001 each additional precheck, under an agreed cap. There is no per-agent surcharge within the agreed workflow and prototype limits. Documentation and this client are free. Human support, setup and engineering are separately agreed. The current real sandbox adapter creates generated folders inside a dedicated Google Drive test folder.
Request a Starter integration with one workflow, a technical owner and a harmless sandbox. No production credentials or sensitive customer data, please.