Terms of Use

Draft status

These proposed terms are not a finalized launch agreement. The contracting operator, contact channel and governing jurisdiction have not been specified. They require legal review before public commercial use. This draft does not replace rights that cannot lawfully be excluded.

Test environment only

The current service supports Solana devnet and test USDC only. Mainnet is disabled. Do not send real funds, mainnet assets or assets from other networks to agent addresses. Devnet state and test assets can be reset or become unavailable. This preview is not a bank account, investment product or promise of a future launch date.

Wallet access and agent authority

Signing a login challenge proves control of a wallet and creates a session; it does not transfer funds. Creating an agent creates a separate service-managed signing key and access token. Keep the token secret: anyone holding it can request payments within the policy enforced by the service.

You choose spending limits and approved vendor origins and recipient addresses. Verify these carefully. The service, not your connected wallet, signs agent payments after checking the policy. Agent wallets in this build are not self-custodial. There is no completed withdrawal or key-recovery flow; do not entrust them with valuable assets.

Payment execution

A merchant can return HTTP 402 with payment requirements. The SDK requests an authorization, submits the signed payload to the merchant, and attempts receipt reconciliation. Authorization is not proof of settlement or delivery. The merchant or facilitator broadcasts the transaction; the service verifies the finalized transaction message before marking it settled.

Outstanding authorizations reserve budget until their outcome is verified. A timeout can leave the result unknown. Keep the original request ID and reconcile before retrying; a new request ID may authorize an additional payment. Request idempotency does not guarantee that a merchant performs a paid action only once.

Pause and revocation prevent new authorizations; they cannot reliably cancel signatures already issued or reverse finalized transfers. The dashboard is not a guarantee that a vendor will deliver accurate or useful data.

Vendors and fees

You decide which vendors your agent may use. Verify their prices, content, permitted uses and refund arrangements independently. The current exact-payment flow validates the merchant's amount and approved fee payer. No production subscription, platform fee schedule or refund policy has been launched. Any future charges must be disclosed before activation.

Responsible use

Use only wallets and credentials you are authorized to control. Do not use the service for unlawful activity, fraud, unauthorized access, attacks on infrastructure, or attempts to bypass other users' policies. Do not send another person's secrets or personal information in resource URLs or agent configuration. Operators may need to restrict access to protect the service or meet legal obligations; operational procedures must be finalized before launch.

Risks and availability

Software bugs, compromised credentials, infrastructure failures, vendor errors and network outages can cause failed, delayed or duplicate economic outcomes. The preview has not completed independent security review or a funded end-to-end acceptance test. No uninterrupted availability, fitness for production or cryptographic privacy is promised.

The service should not be used for critical workloads or assets you cannot afford to lose. These disclosures do not exclude liability or remedies that applicable law does not permit an operator to exclude. Jurisdiction-specific liability and dispute provisions remain subject to review.

Stopping use and future releases

You may stop using the SDK or MCP server and sign out of the dashboard. Signing out does not revoke agent tokens or cancel existing authorizations. Pause agents separately. Data retention is described in the draft Privacy Policy.

A mainnet release requires a separate readiness decision, finalized legal documents and explicit network configuration. These draft terms do not authorize mainnet payments or automatically enroll you in a future paid service.