Terms of Service
1. Acceptance
By registering an Agent or Provider on jecp.dev, or by invoking any endpoint at jecp.dev, you agree to these Terms.
The JECP protocol specification (github.com/jecpdev/jecp-spec) is licensed Apache 2.0 and is not governed by this document. These Terms apply only to the Hub operated by Tufe Company at jecp.dev.
2. Accounts
2.1 Agent accounts
An Agent is registered via POST /api/agents/register and receives an agent_id and api_key. You are responsible for:
- Keeping
api_keyconfidential. Treat it like a Stripe secret key. - All calls made under your
agent_id, whether authorized by you or made possible by your failure to secure the key. - Setting Mandate budget caps appropriate to your risk tolerance. Tufe Company is not liable for over-spending by autonomous agents that you control.
2.2 Provider accounts
A Provider is registered via POST /v1/providers/register. To activate, you must:
- Verify ownership of the domain hosting your endpoint via DNS TXT record.
- Connect a Stripe Express account (subject to Stripe's own Connected Account Agreement).
- Publish a manifest declaring capabilities, actions, and pricing.
You represent and warrant that:
- You have the right to offer the services described in your manifest.
- Your endpoint will respond to invocations within the SLAs you publish.
- You will not use the Service to facilitate illegal activity, including but not limited to: unauthorized access to systems, fraud, malware distribution, or content that violates applicable law.
3. Wallets and payments
3.1 Top-up
Agents may top up wallets at fixed denominations of $5, $20, or $100 USD via Stripe Checkout. Top-ups are non-refundable except as required by applicable law (see §3.4).
3.2 Per-call charging
Each successful capability invocation atomically debits the Agent's wallet by the amount declared in the Provider's manifest. Failed calls (status: "failed") are not charged.
3.3 Revenue split
For each successful, paid invocation:
- 85% is allocated to the Provider's Stripe Connect account
- 10% is retained by Tufe Company as the Hub fee
- 5% is allocated to payment processing (Stripe fees + reserve)
Allocations occur atomically with the wallet debit. Stripe Transfer payouts to Provider accounts are scheduled monthly (this transfer mechanism is on roadmap for Q3 2026; until then balances are accumulated and reconciled manually upon Provider request).
3.4 Refunds
If a Provider's endpoint fails to honor a capability that was charged, the Agent may request a refund within 30 days by emailing hello@jecp.dev with the transaction_id. Tufe Company will investigate in good faith and, where the charge was clearly undelivered, credit the Agent's wallet from the Provider's allocated share. Tufe Company is not obligated to refund where the Provider delivered the action as specified, even if the Agent regrets the call.
3.5 Currency
All prices are denominated in USD. JECP uses "USDC" as a unit of account but settlement happens via Stripe (USD or local currency to Provider's bank).
4. Acceptable use
You may not use the Service to:
- Make threatening, harassing, or unlawful invocations
- Reverse-engineer the Service to extract another user's wallet balance, api_key, or transaction history
- Bypass rate limits via Sybil attack (multiple registrations)
- Resell or sub-license JECP api_keys without disclosure
Tufe Company may suspend any Agent or Provider account that we reasonably believe is in violation of these Terms, with or without notice.
5. Trust Gate
Some capabilities require a minimum Trust Tier (Bronze/Silver/Gold/Platinum) earned by call history. Tier assignment is automated. Tufe Company reserves the right to adjust the algorithm; current rules are documented in spec §5.
6. Service availability
The Service is provided "as is" and "as available." Target availability is 99.5% monthly, but Tufe Company makes no contractual SLA at this time. Maintenance windows are announced when feasible.
7. Indemnification
You agree to indemnify and hold Tufe Company harmless from claims, damages, and expenses arising from:
- Your breach of these Terms
- Your manifest's representations being false
- Content you cause to be processed via JECP capabilities (e.g., a Provider doing OCR on personally-identifiable text the Agent fed it without authorization)
8. Disclaimer of warranties
Tufe Company disclaims all warranties to the maximum extent permitted by applicable law, including merchantability, fitness for a particular purpose, and non-infringement. The protocol specification is open source and not guaranteed to be production-ready for all use cases.
9. Limitation of liability
To the maximum extent permitted by law, Tufe Company's aggregate liability arising out of these Terms or use of the Service shall not exceed (a) the total amount you paid to Tufe Company in the 12 months preceding the claim, or (b) USD $100, whichever is greater.
10. Changes to these Terms
Tufe Company may update these Terms from time to time. Material changes will be notified via email to registered Agents and Providers at least 14 days in advance. Continued use after the effective date constitutes acceptance.
11. Governing law
These Terms are governed by the laws of Japan, without regard to conflict-of-law principles. Disputes shall be resolved in the Tokyo District Court.
12. Contact
Tufe Company Inc.
Tokyo, Japan
hello@jecp.dev
See also: Privacy Policy · Apache 2.0 License