Give every customer a persistent AI agent, inside your own product.
You bring the agent package. ACTA runs the compute, memory and lifecycle.
Your team builds the experience. ACTA keeps each customer's agent, context and runtime connected between tasks.
Resolve each user to a durable agent identity. Route the next message back to the same context.
memory/skills/files/Memory, files and configuration remain available across process restarts and sleep/wake cycles.
Wake, suspend and restart an agent through the API. Keep future work in a persisted wake schedule.
Delegate work, request wakes and inspect status with scoped service keys. Keep your customer experience in your own product.
curl -sS -X POST "$ACTA_BASE_URL/v1/principals/$PRINCIPAL_ID/delegations" \
-H "x-acta-key: $ACTA_SERVICE_KEY" \
-H "idempotency-key: msg_123" \
-H "content-type: application/json" \
--data '{"source":"api","sourceMessageId":"msg_123","text":"Research this account and prepare a brief."}'Authenticate your backend with scoped credentials.
Use a customer identity to provision a runtime and delegate tasks.
Inspect health, results and recorded usage in the console.
Bring your instructions, skills, policies and tool requirements in a versioned package. Give every customer's agent the same starting point, with its own continuing state.
Explore the lifecycleView runtime health, delegation results, stored agent state and recorded usage in your workspace.
Open your consoleSelf-service billing is not yet available. Usage visibility is available in the console.
Software companies building products where each customer needs an agent with continuing memory, files and tools. Your company integrates ACTA; your customers stay in your product.
Your customer experience, agent instructions, skills, policies, approved integrations and model configuration. ACTA operates the runtime and keeps it associated with the customer's persistent agent identity.
No. Runtime compute can suspend or stop between tasks while persistent state is retained. Use the lifecycle API to wake it for the next task.
No. It is an interactive lifecycle illustration. Sign in to the console to inspect your workspace's actual agents, runtime state and recorded activity.