---
name: sleepearn-payments
description: Discover SleepEarn subscription pricing, authenticated checkout modes, referral-credit coverage, NOWPayments USDT payments, and agent-payment protocol boundaries.
---

# SleepEarn Payment Discovery

Use this skill when an agent needs to explain how a SleepEarn subscription is
purchased or determine whether an automated agent-payment protocol is available.

## Implemented Purchase Flow

SleepEarn uses an authenticated, human-present checkout for paid SaaS
subscriptions. The buyer must sign in, select a plan and billing cycle, and
explicitly confirm the purchase in the SleepEarn web application. Checkout then
uses one of two modes:

- Credit-only: when eligible referral credit and/or a prorated upgrade refund
  fully covers the plan price, SleepEarn applies that value and activates the
  subscription immediately. No NOWPayments order or wallet transfer is created.
- On-chain: when a balance remains, the buyer chooses a supported USDT network.
  Eligible credit may reduce the charge, subject to the gateway minimum.
  NOWPayments creates a one-time payment address and amount. The buyer transfers
  USDT from their own wallet; SleepEarn activates the subscription only after the
  gateway confirms settlement by its signed webhook or status API.

- Pricing and plan selection: https://sleep-earn.com/pricing
- Registration: https://sleep-earn.com/register
- Login: https://sleep-earn.com/login
- Authentication notes: https://sleep-earn.com/auth.md
- API documentation: https://sleep-earn.com/docs/api
- Supported billing cycles: quarterly and annual
- Supported USDT networks: TRC-20, Polygon, Solana, ERC-20, and BSC
- Automatic recurring charges: not supported; renewal requires a new checkout

## Agent-Payment Protocol Boundary

As of 2026-07-18, SleepEarn does not expose an unattended agent checkout or a
pay-per-request API. Do not infer protocol support from the use of USDT or from
ordinary HTTP 402 subscription-entitlement responses.

- x402 is not supported: no paid HTTP resource, x402 challenge, payment
  signature, facilitator verification, or same-request resource release exists.
- MPP is not supported: no Machine Payments Protocol challenge, credential, or
  paid resource delivery flow exists.
- UCP is not supported: no Universal Commerce Protocol profile, service,
  checkout capability, payment handler, or `UCP-Agent` negotiation exists.
- ACP is not supported: no Agentic Commerce Protocol checkout-session or
  delegated-payment interface exists.
- AP2 is not supported: no Agent Payments Protocol mandate, signed cart, or
  payment-authorization evidence is accepted.

The absence of these protocol capabilities is intentional. A future discovery
profile must not be published until its corresponding transaction endpoint and
security checks are implemented.

## Safe Agent Behavior

Agents may read public pricing and documentation, then hand control to the user
at the registration, login, or pricing page. Agents must not initiate or confirm
a payment or claim that checkout is unattended. Agents must not request a wallet
private key, seed phrase, NOWPayments secret, bearer token, or Bitfinex API key.