Libramen

Agentic Commerce Terms of Service

Effective Date: August 1, 2026

Version: 2026-08-01

These Agent/API Terms (the “Terms”) govern access to Libramen’s agent-discovery documents, MCP server, plain-HTTP commerce endpoints, hosted transaction-review pages, and related demand-side interfaces (the “Agent Services”). Libramen, Inc. is a Delaware corporation (“Libramen,” “we,” “us,” or “our”).

An “Agent Operator” is the person or entity that deploys, configures, hosts, controls, or calls an AI agent, gateway, API client, or other automated system. A “Buyer” is the person for whom a service transaction is evaluated or confirmed. An “Operator” is the service business selling and delivering that service.

By accessing or using the Agent Services, the Agent Operator accepts these Terms, the Agent/API Acceptable Use Policy (“AUP”), and the Privacy Policy. If the Agent Operator acts for another organization, it represents that it may bind that organization. Buyers accept the separate Buyer Transaction Terms when they use Libramen to make a booking and direct confirmation.

1. Notice through machine-readable surfaces

Libramen publishes links to these Terms, the AUP, the Buyer Transaction Terms, and the Privacy Policy through its gateway schema, hosted llms.txt, MCP information document, MCP server instructions, and published agent skill. Per-Operator documents may also provide available Operator booking, cancellation/refund, and consumer-disclosure links.

Machine-readable notice is part of the Agent Services. The Agent Operator must preserve and present the transaction-specific notice and links in a form the Buyer can understand before confirmation. Endpoint use binds the Agent Operator; buyer contact data by itself does not establish Buyer assent.

2. Authority and buyer approval

The Agent Operator must have authority from the Buyer for every material step it takes. It must not infer authority to purchase merely from browsing, qualification, prior transactions, stored preferences, access to a payment credential, or possession of identity information.

Calling confirm_mandate represents and warrants that the Agent Operator:

  1. is authorized to act for the Buyer for that transaction;
  2. presented the seller identity, immutable service scope, exact total, payment/approval mode, Libramen Buyer Transaction Terms, Privacy Policy, and available Operator policies;
  3. obtained the Buyer’s approval to the specific transaction and payment action; and
  4. accurately supplied the Buyer information the Operator needs to fulfill and support the booking.

Libramen does not require a new attestation field. The representation arises from the confirmation action itself. A credentialless HTTP 402 challenge, payment probe, quote, or APPROVED evaluation is not confirmation and is not recorded as Buyer acceptance.

If Libramen returns an ACTION_REQUIRED hosted-review URL, the Buyer must review and act on the Libramen-controlled page. The Agent Operator must not claim the booking is complete before the resulting payment and booking state says so.

3. Seller and merchant relationship

The identified Operator is always the seller, service provider, and merchant of record. The transaction is between Buyer and Operator. Buyer funds settle to the Operator’s merchant-owned account or configured settlement destination. Libramen facilitates the booking and payment but does not deliver the service, take title to it, or take custody of Buyer funds.

The Operator—not Libramen—controls its services, booking and cancellation terms, refund policy, legally required disclosures, fulfillment, customer support, taxes, ordinary refunds, chargebacks, and disputes. The Agent Operator must not describe Libramen as the seller or merchant of record.

4. Transaction semantics

The Agent Operator must communicate status accurately:

  • REQUIRES_MORE_INFO means the transaction cannot yet be evaluated. Ask only the disclosed question and use the returned opaque continuation mechanism correctly.
  • BLOCKED means the current request cannot proceed. Do not bypass the reason or imply approval.
  • APPROVED is a short-lived quote and payment scope. It is not a booking, payment, reservation, or capacity hold.
  • Successful auto-confirmation creates the booking and reserves applicable Platform-managed capacity.
  • PENDING_APPROVAL is a genuine request awaiting Operator approval. A payment method may be authorized, but authorization is not a slot or capacity hold.
  • A self-scheduled package with a bound session may auto-confirm according to its confirmation mode.
  • An unbound package or by-arrangement service requires Operator approval and does not reserve capacity.
  • CAPTURED, PENDING, FAILED, DECLINED, EXPIRED, refund, and dispute states must be relayed without embellishment.

The Agent Operator must not say “reserved,” “confirmed,” “paid,” or “refunded” unless the returned state supports that statement. In particular, it must never describe a payment authorization as a slot hold.

5. Qualification and transaction integrity

The Agent Operator must provide complete, accurate facts supplied or approved by the Buyer; preserve organization, offering, channel, scope, nonce, and continuation binding; and use idempotency and opaque state as documented. It must not modify encrypted qualification state, answer hidden questions, fabricate eligibility facts, switch organizations or offerings mid-flow, replay single-use state, alter quoted amounts, or use a payment credential beyond the Buyer’s mandate.

The Agent Operator must show the Buyer the exact service, date/time, material options, quantity or duration, Operator, currency, total, and whether payment will be captured immediately or authorized pending approval before confirmation.

6. Buyer information

Current confirmation flows require an ACP-compatible buyer identity record containing email, phone, and name, with optional agent-side customer ID and account classification. The Agent Operator may provide this information only when authorized by the Buyer and must keep it accurate.

Libramen encrypts and stores the accepted Buyer record for the relevant Operator together with the booking and transaction history. The Operator may use it to fulfill and support the transaction, communicate about it, reconcile payment, and address later service issues. The Operator is independently responsible for any later use and applicable communications law. Libramen does not build cross-Operator buyer profiles or operate an Operator marketing-subscription or unsubscribe system.

The Privacy Policy describes Libramen’s processing. Where the Agent Operator independently collects, stores, profiles, or uses Buyer data, it is responsible for its own notice, security, retention, and legal compliance.

7. Payment credentials and hosted checkout

Payment credentials must be handled only through documented confirmation mechanisms and must never be inserted into qualification forms, arbitrary parameters, logs, chat text, or opaque state. Agent-originated hosted checkout remains attributed to the originating MCP or HTTP channel.

Third-party payment-provider and network terms apply. The Agent Operator must not retry uncertain settlement in a way that risks duplicate payment or booking; it must query the mandate status first. Public-network payments may be irreversible and visible on-chain.

8. Availability, errors, and human escalation

Availability, pricing, external calendars, payment settlement, and agent output may be delayed or incorrect. The Agent Operator must stop and seek Buyer input when the returned flow requires it and must direct service, cancellation, fulfillment, or refund questions to the Operator’s support contact.

The Agent Operator must provide a reasonable way for a Buyer to review the proposed transaction before confirmation and to correct erroneous identity or scope information. Where law requires human review or other consumer protections, the Agent Operator and Operator are responsible for providing them for their respective processing.

9. Acceptable use and security

The AUP is incorporated into these Terms. The Agent Operator must protect credentials and state, respect rate and access controls, and report suspected compromise to founders@libramen.ai. Libramen may throttle, block, or suspend access based on security, fraud, legal, provider, or abuse risk.

10. Intellectual property

Libramen owns the Agent Services, schemas, documentation, branding, and related intellectual property. Libramen grants the Agent Operator a limited, revocable, non-exclusive, non-transferable right to access the documented Agent Services for compliant discovery and transaction use. Operator content remains owned by its respective owner.

11. Third-party services

The Agent Services depend on Operators, agents, payment providers, model providers, networks, and infrastructure outside Libramen’s control. Libramen is not responsible for their acts, omissions, availability, or terms except where applicable law does not permit that exclusion.

12. Disclaimers

THE AGENT SERVICES ARE PROVIDED “AS IS” AND “AS AVAILABLE.” TO THE MAXIMUM EXTENT PERMITTED BY LAW, LIBRAMEN DISCLAIMS ALL WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, AND UNINTERRUPTED OR ERROR-FREE OPERATION.

LIBRAMEN DOES NOT WARRANT AGENT AUTHORITY, BUYER IDENTITY, OPERATOR PERFORMANCE, AVAILABILITY, PRICING, PAYMENT SUCCESS, OR THIRD-PARTY SERVICES. NOTHING IN THE AGENT SERVICES IS LEGAL, TAX, FINANCIAL, MEDICAL, SAFETY, OR OTHER PROFESSIONAL ADVICE.

13. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, LIBRAMEN WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, ENHANCED, OR PUNITIVE DAMAGES; LOST PROFITS, REVENUE, DATA, OR BUSINESS; DUPLICATE OR FAILED TRANSACTIONS; CHARGEBACKS; THIRD-PARTY AGENT ACTIONS; OR OPERATOR NONPERFORMANCE.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, LIBRAMEN’S TOTAL LIABILITY ARISING FROM THESE TERMS OR THE AGENT SERVICES WILL NOT EXCEED THE GREATER OF (A) AMOUNTS THE AGENT OPERATOR PAID TO LIBRAMEN IN THE 12 MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM OR (B) USD $100. These limits do not apply where prohibited by law and do not limit a Buyer’s non-waivable rights.

14. Indemnification

To the extent permitted by law, the Agent Operator will defend, indemnify, and hold harmless Libramen and its officers, directors, employees, contractors, affiliates, and agents from third-party claims, damages, liabilities, losses, and reasonable legal fees arising from the Agent Operator’s agent, lack of authority, inaccurate representations, unauthorized data or payment use, violation of these Terms or the AUP, or violation of law.

15. Suspension and termination

Libramen may suspend, restrict, or terminate access for breach, abuse, fraud, security or legal risk, provider requirements, or where required by law. Unpaid mandates expire under their stated terms; suspension does not undo transactions already completed.

16. Changes

Libramen may update these Terms by publishing a new version and effective date through the machine-readable notice surfaces. Continued Agent Service use after the effective date constitutes the Agent Operator’s acceptance. Material changes may require the Agent Operator to update its own buyer notice and transaction flow.

17. Governing law and courts

Delaware law governs these Terms without regard to conflict-of-law principles. The parties will first attempt good-faith negotiation. Any unresolved dispute is subject to the exclusive jurisdiction of the state and federal courts located in Delaware, United States. These Terms do not add an arbitration requirement. Non-waivable consumer rights and mandatory law remain unaffected.

18. Miscellaneous and contact

These Terms, the AUP, and the Privacy Policy are the entire agreement between Libramen and the Agent Operator regarding the Agent Services. If a provision is unenforceable, the remainder remains effective. Failure to enforce is not a waiver. The Agent Operator may not assign these Terms without consent; Libramen may assign them in connection with a merger, acquisition, financing, reorganization, or sale of assets.

Libramen, Inc., 1111B S Governors Ave # 49139, Dover, DE 19904, United States founders@libramen.ai

Publication control: This revision must not be published as effective until external counsel validates agent assent, consumer notice, authority representations, indemnity, liability limitations, and third-party-beneficiary consequences.