Terms of Service
- DO NOT USE REACH IN AN EMERGENCY. Reach is not telephone service. It does not route to 911, 000, 112, or any equivalent emergency number, and it does not guarantee that anyone will answer any call. If you have an emergency, hang up and dial your jurisdiction's emergency number on a regular phone (§5.1, §5.1.1).
- NO RELIANCE. Do not rely on anything surfaced through Reach — capability descriptions, prices, hours, recording-policy declarations, handle or operator identity, voice.json content, or any other third-party- or claimant-supplied data — as a basis for any decision with legal, financial, medical, safety, or commercial consequence. Independently verify before acting (§5.3, §6).
- NO DAMAGES. To the maximum extent permitted by law, InferLane's aggregate liability to you is capped at the greater of (a) fees you paid InferLane in the prior 12 months, or (b) AUD $100. InferLane is not liable for any loss or damage of any kind beyond that cap (§7).
- NO CONSEQUENTIAL OR INDIRECT LOSS OR DAMAGES. InferLane is in no event liable for indirect, incidental, consequential, special, exemplary, or punitive damages — including (without limitation) lost profits, lost revenue, lost data, lost goodwill, lost opportunities, business interruption, procurement of substitute services, or damages for personal injury — even if advised of the possibility (§7).
The rest of the document elaborates on these four points and adds the structural protections (no-sale clarification, no identity verification, force majeure, indemnification, individual arbitration). All of it is binding.
1. Acceptance and parties
These Terms of Service ("Terms") govern your access to and use of Reach by InferLane ("Reach," "Service") across all five distribution surfaces and the inferlane.dev landing page. By installing, accessing, or using Reach you agree to these Terms.
The operator of Reach is InferLane. [Operating entity: to be finalized and disclosed at inferlane.dev/about before public launch.]
You must be at least 18 years old (or the age of majority in your jurisdiction) to use the Service. By using Reach you represent that you meet this requirement.
2. What Reach is
Reach is a universal client for agent-native websites. It reads /.well-known/ agent manifests from any domain and turns the declared capabilities into tools usable by Model Context Protocol (MCP) hosts (Claude Desktop, ChatGPT, browser extensions, the Reach macOS application). For domains that have not published a manifest, Reach maintains a community-curated shadow registry as a fallback.
3. Tiers and licensing
Reach is distributed under a dual posture:
3.1 Open-core (free, perpetual)
- The Reach core, the Claude Desktop Extension, the OpenAI Apps SDK adapter, the browser extension, and the macOS application are released under the Massachusetts Institute of Technology (MIT) license.
- The shadow registry is released under the MIT license. Contributions to the registry are governed by the project's CONTRIBUTING.md.
- You may use, modify, and redistribute the open-core components in commercial or non-commercial contexts subject to the MIT terms.
3.2 Premium Service Level Agreement (SLA) adapters
- InferLane offers a paid premium SLA tier for the top sites in the shadow registry. Premium adapters are maintained with uptime guarantees, change-detection monitoring, and faster sync to upstream API changes.
- Premium adapters are proprietary. Access is granted via subscription. Cancellation policies, refund triggers, and uptime credits are defined in the order form you accept at the time of purchase.
- The InferLane cost-tracking service is available for free use; advanced reporting features (cohort analysis, custom alerts) may require a paid InferLane plan, governed by InferLane's separate terms.
3.3 Reach handle account (personal tier, free)
If you claim a personal Reach handle at inferlane.dev/reach/claim, you additionally agree:
- SMS verification: you authorize InferLane to send you a one-time SMS code to verify control of the phone number you submit. Standard message rates from your carrier may apply; InferLane does not charge for the verification SMS.
- Your handle is a public identifier: your handle, display name, and SIP endpoint appear on a public calling card at
inferlane.dev/@<handle>and in the Bloom-filter snapshot served atapi.reach.inferlane.dev/bloom.bin. Anyone with a Reach client can look you up. Do not claim a handle if you want this to be private. - One handle per number: a phone number can hold at most one active handle at a time.
- Revocation: you may revoke your handle at any time via the dashboard or by emailing privacy@inferlane.dev. Within 7 days the encrypted phone row is deleted; on the next daily snapshot rebuild your lookup hash stops appearing in the Bloom filter.
- Receiving calls is at your discretion: nothing requires you to keep a browser tab open or to accept any call. The
reach-agentclient is what you sign into to take calls; the operator dashboard is what configures hours/voicemail/agents. - You are responsible for the calls you receive through your handle, just as you would be on any other communication channel. Reach is a routing layer, not a moderator. See §4 for prohibited uses.
- SMS notifications are opt-in: the "SMS me when someone tries to reach me while offline" feature (B.5) is off by default. You may opt in or out via the dashboard.
3.4 Operator account (business tier, free at v1.1)
If you sign up at inferlane.dev/reach/operator to operate one or more verified domains, the Reach Operator Agreement applies in addition to these Terms. See operator-agreement.html. By signing up you accept that agreement.
4. Acceptable use
You agree not to:
- Use Reach to violate the terms of service of any third-party website. Reach surfaces capabilities; you remain responsible for the third party's terms.
- Use Reach to perform high-volume scraping, denial-of-service, or other abusive traffic patterns. Reach honors target-site rate limits where declared.
- Use Reach to invoke capabilities you are not authorized to invoke (for example, deleting another person's data).
- Submit shadow-registry entries that violate the project's Acceptable Use Policy.
- Reverse-engineer the premium SLA adapters or attempt to circumvent the subscription gating.
- Use Reach in a regulated context where you have not independently obtained the necessary approvals (for example, healthcare actions, securities trading, banking transfers).
5. Capability invocation and consent
Reach is a discovery and routing layer. When you invoke a capability through Reach (from Claude Desktop, ChatGPT, your code, the browser extension's clipboard intent, or the Mac app), you are the party calling the third-party service. Reach surfaces, but does not consent on your behalf.
Capabilities are tagged with one of three sensitivity flags:
- read: idempotent retrieval. Auto-invoked by agents without confirmation.
- write: creates or modifies state on the target site. Requires per-invocation user confirmation by default; you can opt into per-domain auto-confirm.
- destructive: permanent state change, payment, deletion. Always requires per-invocation user confirmation. The sensitivity flag cannot be downgraded by the host.
You acknowledge that hosts (Claude, ChatGPT, browsers) implement consent flows differently. Reach is not responsible for ambiguity introduced by host-side user interface implementations. If in doubt, do not invoke a destructive capability.
5.1 Voice signaling and the no-media-in-the-path commitment
Voice calls placed through Reach traverse the InferLane signaling server (voice.inferlane.dev) for SIP signaling only. The audio stream of any call flows browser-to-browser via WebRTC and never traverses InferLane infrastructure. The signaling server's role is bounded to:
- Resolving the dialled domain to its voice manifest (either via the publisher's
/.well-known/voice.json, the shadow registry, or — for the personal-handles namespace — the handles backend). - Looking up which agent (if any) is currently registered for the dialled endpoint.
- Routing the SIP INVITE accordingly, or rejecting with a SIP status code.
- Logging per-call metadata as listed in the Privacy Policy §3.5.6.
If a caller is behind symmetric NAT, the WebRTC media path may briefly transit a Traversal Using Relays around NAT (TURN) server operated by InferLane. The TURN server is configured with no-log; it relays packets without decoding or storing them.
You agree that InferLane is not a common carrier, is not a telecommunications service, and is not subject to obligations imposed on telcos (CALEA, STIR/SHAKEN attestation, regulated 911 service, lawful-intercept compliance). Reach is a software signaling layer between consenting WebRTC endpoints.
5.1.1 DO NOT USE REACH IN AN EMERGENCY
- Reach does not route to 911 (United States), 000 (Australia), 112 (European Union, United Kingdom, India), 119 (Japan, Korea), 999 (Hong Kong, Saudi Arabia), 100 (Israel) or any other public emergency number.
- Reach does not provide caller location information to any emergency dispatcher.
- Reach does not guarantee that any specific handle, endpoint, agent, or operator will answer at any specific time, including during emergencies. Even endpoints labelled "support", "emergency", "urgent", or similar may be unstaffed, offline, behind a malfunctioning WebRTC stack, behind a NAT we cannot traverse, or otherwise unreachable.
- Reach is implemented as a browser-to-browser WebRTC session over a software signaling layer. It depends on functional internet connectivity, a functional browser audio subsystem, a functional remote agent, and a functioning third-party signaling infrastructure. None of these is guaranteed.
- InferLane disclaims, to the maximum extent permitted by law, all liability for any harm — including personal injury or death — arising from any attempt to use Reach as a substitute for an emergency-services call.
If you or another person is in danger, stop using Reach and call your jurisdiction's emergency number from a regular phone immediately.
5.2. Reach does not sell goods or services
When you invoke a capability or place a call through Reach, you contract directly with the third-party publisher of that capability or with the holder of the personal-tier handle you dialled. InferLane is neither party to that contract, nor your agent in it, nor the publisher's agent. No statement made by InferLane (in code, in marketing copy, in support correspondence, or anywhere else) creates a contract between you and any third party.
Where InferLane operates a paid tier (e.g. a future premium Service Level Agreement adapter, or premium operator features), the corresponding order form or pricing page is the source of truth for what InferLane is selling and on what terms. That is separate from anything surfaced by the discovery/signaling layer.
5.3. No reliance on third-party data surfaced through Reach
The "information surfaced through Reach" referenced above includes, without limitation:
- Capability identifiers, names, descriptions, parameter schemas, output schemas, and human-readable text in any manifest.
- Sensitivity flags (
read/write/destructive) — these are publisher-asserted. A capability labeledreadmay in fact have side effects InferLane has not detected. - Cost estimates declared in a manifest. They may be outdated, incomplete, currency-mislabelled, or wrong. The actual charge for any third-party action is set by that third party at the time you invoke it; that price may differ from the estimate and may change without notice.
- Availability statements, including business hours, agent on-shift counts, voicemail availability, and estimated wait time. Operators set these in configuration; reality may diverge.
- Recording policies declared by an endpoint. The declaration is informational. InferLane does not enforce the publisher's actual recording practice; the publisher does (and is responsible for compliance with applicable call-recording law in their and the caller's jurisdiction).
- Publisher and handle metadata — name, display name, description, calling-card avatar, contact information. Phone-number verification (handles) and DNS-TXT verification (operator publishers) confirm control of the verified resource; they do not confirm the legal identity, trade name, authority, regulatory status, licence to operate, trustworthiness, solvency, or good faith of the holder.
- Trust signals, badges, "verified" indicators, and similar visual flourishes in the Reach client surfaces. These reflect the technical-verification facts above and nothing more.
- Shadow registry entries — community-curated, best-effort, may lag the upstream API.
- Synthesized
voice.jsondocuments — the JSON content is generated from operator-supplied configuration; InferLane does not audit it for accuracy.
If you are acting on Reach data in a regulated context (banking, healthcare, securities, alcohol/tobacco/firearms, gambling, child-directed services), you must independently verify the relevant facts through channels appropriate to that context. Reach is not a regulatory-compliance tool.
5.4. No identity verification
Different surfaces use different verification mechanisms; none of them establish legal identity:
- Personal handles: phone-number ownership only. The claimant proved at one point they could receive an SMS at a number; nothing more. Display name is whatever the claimant typed. Avatar is generated. You should not assume @some-handle is the celebrity, business, or public figure whose name appears on the card unless that party tells you so on a channel you trust.
- Operator publishers: DNS-TXT control of the domain only. Whoever controlled the DNS zone at the moment of the TXT query proved access to that zone. They may not be the legal owner of the underlying business, brand, or company name associated with the domain. DNS ownership can also transfer; we do not re-verify continuously.
- Operator agents: a SIP REGISTER credential generated by the operator. The operator's invite + revoke decisions are the only check.
- Callers: not verified at all by InferLane. The caller's Reach client may send a display-name hint, which is unverified user-supplied text.
Treat any party reached through Reach with the same care you would extend to a cold email or an anonymous web form — until you have authenticated them out-of-band.
5.5. No availability guarantee
InferLane does not guarantee that any third-party service, capability, endpoint, agent, operator, publisher, or handle will be available at any given time. Site downtime, agent absence, manifest staleness, DNS or network failures, third-party API changes, rate limiting, abuse blocks, regional outages, and similar conditions are normal and outside InferLane's control. The Reach signaling and handles services themselves are provided on a best-effort basis at v1.x with no SLA.
6. Disclaimers
Without limiting the foregoing, InferLane does not warrant:
- the accuracy, completeness, currency, legality, safety, suitability, or fitness for any purpose of any information surfaced through Reach (see §5.3 for the non-exhaustive list of what that includes);
- that any price, fee, or cost shown in a manifest, on a calling card, in a capability description, or in any Reach-rendered surface matches what the third party will actually charge — that price is set by the third party;
- that any third-party service, capability, endpoint, agent, operator, or handle holder is available, reachable, responsive, online, in business, regulated, licensed, lawful in your jurisdiction, or willing to deal with you;
- that any capability invocation, voice call, signaling exchange, or notification SMS will succeed, deliver, connect, complete, be timely, be heard, be answered, or produce a particular result;
- that recording, transcription, captioning, monitoring, retention, or deletion claims made by a third-party publisher correspond to that publisher's actual practice; the publisher is responsible for the truth of those declarations and for compliance with applicable law;
- that the identity of any handle holder, operator, agent, publisher, or caller is what it appears to be (see §5.4);
- that the Reach open-core software, shadow registry, signaling server, handles backend, operator dashboard, or any other component is uninterrupted, error-free, free from harmful components, or will continue to be supported indefinitely.
Where a paid premium SLA tier is in effect, the warranties and remedies for that tier are defined in the corresponding order form and apply only to that tier's specific adapters or services. Nothing in a premium order form extends warranties to the open-core surfaces, the shadow registry, or any third-party content.
Statutory consumer guarantees. Some jurisdictions (including Australia under the Australian Consumer Law) provide non-excludable consumer guarantees. To the extent such a guarantee applies and cannot lawfully be excluded, InferLane's liability for breach is limited, at InferLane's option, to (a) supplying the services again, or (b) paying the cost of having the services supplied again. Nothing in these Terms is intended to exclude or limit a right or remedy that cannot lawfully be excluded.
7. Limitation of liability
Without limiting the foregoing, InferLane is not liable for:
- Loss or damage arising from your reliance on any information surfaced through Reach, including capability descriptions, sensitivity flags, cost estimates, availability statements, recording policies, hours, handle or operator identity, calling-card content, or any other publisher- or claimant-supplied data (see §5.3).
- Loss or damage arising from any third party's act or omission, including a third-party publisher's billing, refusal to deliver, breach of contract with you, breach of its own published terms, inaccurate manifest, downtime, or unlawful act.
- Loss or damage arising from a handle holder's, operator's, agent's, or caller's conduct, content, or statements during a call placed through the Reach signaling layer.
- Loss or damage arising from a third-party platform on which Reach is distributed (Claude Desktop, ChatGPT, the Chrome Web Store, the Apple App Store, your operating system) ceasing to support, removing, suspending, or disabling Reach or any feature of Reach.
- Loss or damage arising from denial, failure, delay, or quality of any voice call, SMS notification, or WebRTC media exchange.
- Loss or damage arising from a third-party action being illegal in your jurisdiction, where the action was permitted in the publisher's jurisdiction.
- Loss or damage arising from the matters listed in §10.4 (force majeure).
Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages. Where such exclusion is not permitted, InferLane's liability is limited to the maximum extent allowed by applicable law. Where mandatory consumer protection law in your jurisdiction provides remedies that cannot be waived by contract, those remedies apply notwithstanding this section.
8. Indemnification
You agree to indemnify, defend, and hold harmless InferLane and its officers, directors, employees, contractors, and agents from and against any claim, demand, action, proceeding, loss, liability, damage, cost, or expense (including reasonable legal fees on a solicitor-and-own-client basis) arising out of or relating to:
- Your use of Reach in violation of these Terms, the Operator Agreement (if applicable), the Acceptable Use Policy, the EULA (if applicable), or any law applicable to you.
- Your invocation of a third-party capability that you were not authorized to invoke, or that you invoked in breach of the third party's own terms.
- Your reliance on any information surfaced through Reach — including, without limitation, capability descriptions, sensitivity flags, cost estimates, business hours, availability statements, recording policies, handle or operator identity, calling-card content, and any other publisher- or claimant-supplied data — without independent verification (see §5.3).
- A claim by any person that you misrepresented your identity, authority, or status through a Reach handle, operator account, agent credential, display name, or any other surface you control.
- A claim by any person concerning content transmitted by you, or on your behalf, during a Reach call (audio, transcript, file, or other), including but not limited to defamation, harassment, fraud, IP infringement, unlawful recording, unlawful disclosure of personal information, or breach of confidentiality.
- Your operation of a Reach handle or operator publisher in a manner that violates a third party's intellectual property, privacy, publicity, or contractual rights.
- Content you submit to the shadow registry that infringes a third party's intellectual property rights or violates a target site's terms of service.
- Any tax, duty, fee, or charge imposed on a transaction in which you used Reach as a discovery or signaling layer.
InferLane reserves the right, at your expense, to assume the exclusive defence and control of any matter subject to indemnification by you. You agree to cooperate with InferLane's defence of any such claim. You will not, without InferLane's prior written consent, settle any such claim in a way that imposes any non-monetary obligation on InferLane or admits any fault on InferLane's behalf.
9. Termination
You may stop using Reach at any time by uninstalling it. For the hosted ChatGPT endpoint, your session is automatically terminated 30 minutes after your last interaction.
InferLane may suspend or terminate your access to the hosted services (the ChatGPT endpoint, the registry CDN, premium SLA adapters) at any time if you materially breach these Terms. InferLane will provide reasonable notice unless the breach poses an immediate risk (security incident, regulatory order).
The open-core software is licensed under the MIT license, which is perpetual. Termination of these Terms does not revoke your MIT license rights to the open-core code.
10. Governing law and dispute resolution
These Terms are governed by the laws of New South Wales, Australia, excluding its conflict-of-laws rules. Mandatory consumer protection laws of your country of residence apply to the extent they cannot be waived by contract.
10.1 Binding individual arbitration
Any dispute arising out of or relating to these Terms or your use of Reach that cannot be resolved by good-faith negotiation within 30 days will be resolved by binding individual arbitration administered by the Australian Centre for International Commercial Arbitration ("ACICA") under its Expedited Arbitration Rules. The seat of arbitration is Sydney, Australia. Each party bears its own legal costs unless the arbitrator finds the claim frivolous.
10.2 No class actions, mass arbitrations
You and InferLane agree that disputes will be resolved on an individual basis only. You may not bring or participate in:
- A class action, collective action, or representative action.
- A mass arbitration in which 25 or more claimants present substantially similar claims through the same counsel or organizing party. Where 25 or more such claims are filed, the parties agree to (a) a sequential cost-allocation under which the claimant batch is responsible for the arbitration administrator's pre-hearing fees if a sample of claims is found to be unsupported, and (b) bellwether process: the first ten claims proceed individually; the remainder are stayed pending the outcome.
This provision exists to discourage organized claim-farming practices that have been used against other operators (for example, DoorDash, Uber). It does not affect your right to bring an individual claim.
10.3 Right to opt out
You may opt out of the binding-arbitration clause in §10.1 by emailing legal@inferlane.dev within 30 days of first using Reach with the subject line "Arbitration Opt-Out." The opt-out has no other effect on these Terms.
10.4 Force majeure
InferLane shall not be liable for, and is excused from performance with respect to, any failure or delay in performance arising from causes beyond its reasonable control, including (without limitation) acts of God, fire, flood, earthquake, pandemic or other public-health emergency, war, terrorism, civil unrest, government order, regulatory action, sanctions, court order, internet or power outage, third-party platform or infrastructure failure (including Fly.io, Vercel, Cloudflare, Twilio, Apple App Store, Google Chrome Web Store, Anthropic, OpenAI, or any successor or equivalent provider), cyber-attack, denial-of-service event, ransomware, supply-chain disruption, labour action, or any other event of force majeure. During any such event, time for InferLane's performance is extended for the duration of the event; if the event persists for more than 30 days, either party may terminate the affected hosted service on notice without further liability.
10.5 Survival
The following sections survive termination of these Terms: §3 (Tiers and licensing — to the extent of MIT license rights), §5.2 (No sale), §5.3 (No reliance), §5.4 (No identity verification), §5.5 (No availability guarantee), §6 (Disclaimers), §7 (Limitation of liability), §8 (Indemnification), §10 (Governing law and dispute resolution), §11 (Changes), and §12 (Miscellaneous).
11. Changes to these Terms
InferLane may update these Terms. Material changes will be notified via a banner on inferlane.dev and (if you have an InferLane account) by email at least 30 days before they take effect. Your continued use of Reach after the effective date constitutes acceptance.
12. Miscellaneous
Entire agreement. These Terms (together with the Privacy Policy, the Operator Agreement if you operate a verified domain, the Acceptable Use Policy, the EULA if you install the macOS application, and any order form for premium SLA adapters) constitute the entire agreement between you and InferLane regarding the Service, and supersede any prior or contemporaneous representations, oral or written, regarding the same subject matter.
Severability. If any provision of these Terms is held invalid or unenforceable, the remaining provisions remain in effect.
No waiver. InferLane's failure to enforce any right or provision is not a waiver of that right or provision.
Assignment. You may not assign these Terms without InferLane's prior written consent. InferLane may assign these Terms to a successor entity (for example, in a sale, merger, or reorganization).
Notices. InferLane may give notice via email or by posting to inferlane.dev. You may give notice to InferLane by emailing legal@inferlane.dev.