Acceptable Use Policy

Version: 2026-08-01

This Agent/API Acceptable Use Policy (“AUP”) applies to every AI agent, gateway, API client, person, or automated system that accesses Libramen’s discovery, MCP, plain-HTTP commerce, hosted review, or related demand-side services. It is incorporated into the Agent/API Terms.

The person or entity that deploys, configures, hosts, controls, or calls the agent or client is the “Agent Operator.” The Agent Operator is responsible for its users, credentials, agents, and requests.

1. Lawful and authorized use

The Agent Operator must not use Libramen to:

• violate law, regulation, sanctions, export controls, payment-network rules, or third-party rights;
• facilitate fraud, deception, unauthorized payments, identity misuse, money laundering, bribery, evasion, or harmful activity;
• purchase or facilitate illegal services or regulated services that the Operator or Platform does not support;
• impersonate a Buyer or Operator, misstate authority, or confirm a transaction without the Buyer’s specific approval;
• supply false identity, eligibility, qualification, payment, or transaction information; or
• collect, disclose, infer, or use personal information without authorization and any legally required notice.

2. Transaction integrity

The Agent Operator must not:

• alter or conceal the seller identity, service scope, price, tax, total, status, policy links, or payment/approval mode shown by Libramen;
• treat an APPROVED quote, payment authorization, pending request, or credentialless payment probe as a confirmed booking or capacity hold;
• manipulate opaque continuation state, signed review tokens, mandate tokens, scope fingerprints, organization binding, channel attribution, nonce, expiry, or idempotency controls;
• replay, duplicate, race, or retry transactions in a manner likely to create duplicate bookings or payments;
• bypass required Buyer questions, eligibility rules, availability checks, Operator approval, or human review; or
• place payment credentials in chat, qualification answers, arbitrary parameters, logs, or any field not documented for payment confirmation.

3. Security and system integrity

The Agent Operator must not:

• gain or attempt unauthorized access to accounts, organizations, data, credentials, systems, or third-party integrations;
• defeat or circumvent authentication, authorization, rate limits, payment controls, access boundaries, robot controls, or other safeguards;
• probe, scan, exploit, disrupt, overload, degrade, or interfere with Libramen or connected services;
• introduce malware, malicious prompts, harmful payloads, spam, phishing, credential harvesting, or deceptive content;
• conceal request origin or rotate identities, addresses, sessions, or clients to evade restrictions; or
• publish or exploit a vulnerability before Libramen has had a reasonable opportunity to address it.

Report suspected vulnerabilities or compromise to founders@libramen.ai.

4. Unauthorized extraction and misuse

The Agent Operator must not access, extract, scrape, reproduce, aggregate, republish, sell, or use Libramen or Operator information except as authorized by the documented interface, the relevant Operator, or applicable law. It must not circumvent measures intended to limit automated access or use information obtained through Libramen to harm, profile, discriminate against, or compete unfairly with an Operator or Buyer.

Information deliberately exposed through public discovery or transaction surfaces may be accessed by authorized agents for genuine buyer discovery and transactions. That permission does not authorize bulk extraction, unrelated reuse, or circumvention.

5. Buyer protection

The Agent Operator must:

• present material transaction facts and legal links clearly before confirmation;
• obtain Buyer approval for the exact service and amount;
• give the Buyer a reasonable opportunity to correct errors;
• communicate returned booking, payment, approval, refund, and dispute states accurately;
• protect Buyer information and use it only for authorized purposes; and
• direct service, fulfillment, cancellation, and ordinary refund issues to the relevant Operator.

The Agent Operator must not use manipulative interfaces, hide material terms, fabricate urgency, or cause a Buyer to approve a materially different transaction.

6. Fair use and attribution

The Agent Operator must follow published technical documentation, identify its client and model accurately when attribution fields are available, maintain reasonable request rates, cache where instructed, and stop retrying when Libramen returns a terminal or security response.

Libramen may impose or change reasonable usage limits to protect Buyers, Operators, infrastructure, payment providers, and service reliability.

7. Enforcement

Libramen may investigate suspected violations and may throttle, block, suspend, or terminate an agent, client, IP address, transaction pattern, organization, or other access path. Libramen may preserve evidence and cooperate with Operators, payment providers, law enforcement, or regulators where legally permitted or required.

Enforcement does not obligate Libramen to monitor every request and does not make Libramen responsible for the Agent Operator’s conduct.

8. Changes and contact

Libramen may update this AUP by publishing a new version and effective date through its legal and machine-readable notice surfaces. Continued use after the effective date constitutes acceptance by the Agent Operator.

Questions and reports: founders@libramen.ai

Publication control: This revision must not be published as effective until external counsel confirms that the enforcement, extraction, consumer-protection, and security provisions are appropriate for the live Agent Services.