Agent Use Policy

1. Who This Policy Applies To

Anyone who operates an AI agent that:

• Buys Bips directly, or receives them through the HTTP 402 Payment: bips flow.
• Consumes the Bippsi MCP server at /api/v1/mcp or its /mcp alias.
• Responds to Bippsi paywall headers on any Bippsi-connected site.
• Interacts with the Bippsi pricing manifest at /bippsi-unified.md or any agents.json file on a connected site.

The Policy applies whether the agent is autonomous, human-supervised, or scripted — and whether it acts under an individual's account or a business's account.

2. Nature of Bips and Unlocks

This section is foundational — read it carefully because it controls how you may interpret every other part of this Policy.

• Bips are usage credits, not money. A Bip is a non-refundable, non-transferable right to initiate a specific number of Unlock events on Bippsi-connected sites. Bips have no cash value, do not represent stored funds, are not redeemable for currency, and are not convertible to any other form of value.
• Bippsi is not a reseller. When you spend Bips at a Partner Site, you pay Bippsi for the Unlock — the metered access event itself. You do not pay Bippsi for the underlying content, product, service, data, or outcome the Partner delivers. The Partner is solely responsible for whatever you receive on the other side of the Unlock.
• All purchases are final. Bip purchases are non-refundable. This is a material term. See Agent ToS Section 5 for the narrow exceptions (fraud, technical errors attributable to Bippsi) where a refund may be issued at Bippsi's sole discretion.
• Bips do not expire. Purchased Bips remain in your balance until spent. Termination of your account forfeits unspent Bips per Agent ToS Section 8.

3. Prohibited Agent Behavior

The following are always prohibited, regardless of how you structure the agent or justify the behavior:

3.1 Chargeback Abuse

• Do not initiate chargebacks, payment disputes, or reversals on Bip purchases you intended to make and that were delivered to your balance.
• Fraudulent chargebacks are grounds for permanent account termination, forfeiture of unspent Bips, and reporting to the card-issuing bank and payment networks.
• Chargeback pass-through per Partner Agreement Section 11 also applies: a fraudulent chargeback may deduct from Creator Earnings at Partner Sites where you spent.

3.2 Credential Resale and Brokering

• Do not sell, rent, broker, or transfer your Bippsi account, API keys, MCP access, or Bip balance to another person or entity.
• Do not operate as an intermediary that buys Bips on behalf of third parties to resell access to Bippsi-connected sites.
• Account sharing between business employees is permitted; account sharing across unrelated parties is not.

3.3 Multi-Account Evasion

• Do not create multiple Bippsi accounts to bypass the first-purchase unlock gate, tier limits, rate limits, or any promotional offer.
• Do not create sub-accounts, synthetic identities, or disposable accounts to evade bans or suspensions.
• If you legitimately need multiple accounts (for example, separate billing entities within a corporate group), disclose this to Bippsi via the contact form and we will configure it properly.

3.4 Paywall and Auth Bypass

• Do not use Bippsi to circumvent paywalls, login walls, licensing, anti-bot controls, or any access control on sites that have not opted into the Bippsi program. Bippsi is only authorized to meter access on sites whose owners have registered and consented.
• Do not use your Bip balance to justify non-consensual access to third-party sites. A Bip is an Unlock at a Partner Site, not a license to bypass any paywall you encounter.
• Respect robots.txt, HTTP 429 rate limits, and any sign-up/auth requirements a site places on you. Bippsi does not override these.

3.5 Pricing Manipulation

• Do not attempt to manipulate published Bip prices by coordinating with Partners, exploiting race conditions in price changes, or pre-fetching manifests to freeze-old-prices past the 24-hour stability window.
• Do not coordinate with Partners to split a single large transaction into multiple priced elements to evade the 125-Bip per-interaction cap.
• If you believe a Partner is abusing pricing or the price cap, report it via contact form rather than exploiting the gap.

3.6 Data and Privacy Abuse

• Do not use Bippsi or Bip-unlocked endpoints to scrape, aggregate, or resell personal data in a manner that violates the target Partner's terms or applicable privacy law.
• Do not use agent-driven access to build datasets for training models without complying with the target Partner's licensing and the rules in the Partner Agreement.
• Do not use Bippsi to impersonate real humans, generate deepfakes, or execute social-engineering campaigns.

3.7 Infrastructure Abuse

• Respect documented rate limits on the MCP server and REST APIs.
• Do not issue excessive concurrent connections, retries, or burst traffic designed to starve other agents.
• Do not use Bippsi as a relay or proxy for traffic unrelated to agent monetization.

4. Verification Obligations

Higher-value Bip tiers and certain services require identity or business verification. When Bippsi asks for verification:

• Provide accurate and current information. Material misrepresentation is grounds for permanent termination and law-enforcement referral.
• Consent to Bippsi's verification provider(s) processing the data necessary to complete the check. See the Privacy Policy for the list of processors and data flows.
• Do not attempt to forge, recycle, or share verification artifacts (ID images, selfies, business documents).
• Verification status is tied to your Bippsi account and may not be transferred or resold.

5. MCP Server Hygiene

When consuming the Bippsi MCP server at /api/v1/mcp:

• Use your own Bippsi API key. Keep it out of source control, logs, and public repositories.
• Do not publish or share MCP tool output that contains other users' data, internal identifiers, or credentials.
• Honor the 402 Payment Required flow. Agents must obtain an explicit Bip allowance from the human operator before spending above trivial thresholds — enforce this at your client layer.
• Report reproducible MCP bugs via the contact form with subject "MCP bug report".

6. Reporting Misconduct

If you observe misconduct by another agent, a Partner, or the platform itself, report it via the contact form. Good-faith reports are protected; retaliation against a good-faith reporter is itself a material breach of this Policy and the Agent ToS.

7. Enforcement and Consequences

Violations of this Policy trigger one or more of the following, at Bippsi's sole discretion, in addition to any consequences under the Agent ToS:

• Warning and required corrective action within a stated timeframe.
• Suspension of API keys, MCP access, or Bip spending while an investigation is pending.
• Permanent account termination. Unspent Bips are forfeited per Agent ToS Section 8.
• Retention of account data, request logs, and verification records for evidence and compliance, notwithstanding any deletion request.
• Reporting to law enforcement, regulators, and affected Partners.
• Civil recovery of any damages Bippsi or affected Partners incur as a result of your conduct.

Bippsi's determination of whether a violation has occurred, and of the appropriate response, is final. You waive any right to arbitration or appeal of enforcement decisions except as required by non-waivable law.

8. Changes to This Policy

We may update this Policy at any time. Changes are posted on this page with an updated "Last updated" date. Material changes are communicated via email to your registered account address at least thirty (30) days before they take effect. Continued agent activity after a change takes effect constitutes acceptance.

9. Contact

Questions, reports, or requests for accommodations:

• Contact form: bippsi.com/contact
• Mail: Big App Studio LLC, Glendale, AZ, United States