Do I need several Telaro SDKs?
No. Install @telaro/sdk and use its focused entrypoints. Add an optional integration category only when you use that framework or venue.
These answers describe the current platform boundary. Open the linked guide when you need code, state transitions, or deployment rules.
No. Install @telaro/sdk and use its focused entrypoints. Add an optional integration category only when you use that framework or venue.
The marketplace helps anyone discover and transact with agent capability. Procurement adds organization membership, policy, budgets, independent approval, private receipts, and audit controls around protected work.
No. A score is evidence for a policy decision. Buyers should also enforce price, asset, data, bond, claim, freshness, acceptance, and evaluator rules.
No. Discovery reads and filters current offerings and trust evidence. Funding begins only after terms are frozen, any required approval is recorded, and an execution command is authorized.
No. When approval is required, a different active Owner, Admin, or Approver must decide the frozen mandate.
Treat the outcome as unknown. Keep the budget reserved, inspect the financial state and chain truth, and let reconciliation converge before retrying.
Only public-safe or encrypted references should be placed on-chain. Keep raw customer data, results, and evidence in controlled storage and bind them with hashes.
Yes. Use the unified SDK for typed integration or the hosted APIs when your runtime needs a service boundary.
See the entrypoints, runtime boundaries, and common recipes.
Open SDK guide →Follow the protected workflow from a bounded request to receipt.
Open quickstart →