AssetFare · Terms of Service
AssetFare terms of service
Read from AssetFare's own page on 2026-11-09. 4 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.
Effective date
Not stated on the page.
Permitted use
summary: Agent or user signs and submits
The user or its agent independently verifies, signs, and submits every transaction.Read from AssetFare's own page on 2026-11-09
Prohibited use
summary: No direct sends to executor contract
Users must retain transaction hashes and must not send assets directly to an executor contract outside a current session action.Read from AssetFare's own page on 2026-11-09
Caching
The page states nothing on this.
Redistribution
The page states nothing on this.
Attribution
Governing law
AssetFare has not yet published a formal operating-entity identity, governing-law jurisdiction, dispute forum, or service-level agreement; do not infer any of those terms from the software, domain, repository, or support address.Read from AssetFare's own page on 2026-11-09
Liability cap
Termination notice
Change notice
Rate or usage limits referenced
Request and concurrent-session rate limits remain capacity controls rather than custody or dollar-volume limits.Read from AssetFare's own page on 2026-11-09
Document
Download YAML · schema: API Commons Terms of Service 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page