← Subpay

API Terms of Use

Last Updated: October 5, 2026

1. Acceptance of Terms

These API Terms of Use (“API Terms”) govern access to the document reading API operated by Subpay (a registered DBA of Jones Creek Holdings, LLC) (“Subpay,” “we,” “us,” or “our”) at https://subpay.ai/api/v1/ (the “API”). By sending a request or a payment to the API, you agree to these API Terms. If you do not agree, do not use the API.

The API may be called by software, including automated or AI agents. “You” means the person or organization that operates, deploys, or controls the software or agent making the request, and on whose behalf it acts. You are responsible for every request and payment your software or agent makes, whether or not you reviewed it.

These API Terms are separate from the Terms of Service for Subpay.ai accounts. Using the API does not create a Subpay account and does not give access to any Subpay account or the data in it.

2. What the API Does

The API reads a construction document you submit, such as an AIA G702/G703 or platform pay application, a change order, or a request for change order, and returns figures and classifications read from it, together with automated arithmetic checks and warnings (the “Output”).

The API only reads the document you submit. It does not create records, submit, file, approve, or pay anything, and it does not communicate with any contractor, owner, or payment platform on your behalf.

3. Automated Output — Verify Before Relying on It

Output is generated automatically using artificial intelligence and may be incomplete or incorrect. A successful response, passing checks, or a high confidence score does not mean the Output is accurate. Checks and warnings are aids, not guarantees.

You are solely responsible for verifying every figure and classification against the source document before relying on it for any business, financial, lending, payment, legal, or accounting purpose, including approving, funding, or paying a pay application or change order. The API is not accounting software, a financial system of record, or a substitute for professional review, and we do not provide legal, accounting, financial, or tax advice.

4. Fees and Payment

Each successful read is charged the price stated in the API’s payment-required (HTTP 402) response at the time of your request, currently US $0.20 payable in USDC over the x402 protocol on the networks that response lists. A read is “successful” when the API returns Output with an HTTP status below 400. A successful read is charged even if its Output contains errors or warnings.

Requests that fail and return an HTTP status of 400 or above are not charged; the payment is not settled. Payments are settled on public blockchain networks through a third-party payment facilitator and are final and irreversible once settled. Except where required by law, we do not issue refunds.

You are responsible for your wallet, its security, the networks and assets you choose to pay with, and any taxes, fees, or reporting obligations on your side. We are not responsible for losses caused by your wallet, blockchain networks, stablecoin issuers, or payment facilitators. We may change the price at any time; the price in the 402 response for a request governs that request.

5. Your Documents and Data

You may submit only documents you have the right to share. You represent that submitting a document does not violate any confidentiality agreement, non-disclosure agreement, law, or third-party right. You retain all rights to your documents and to the Output.

You grant us a limited license to process each document solely to produce its Output. Processing includes sending the document to our AI model provider (Anthropic’s Claude API), which processes it to generate the Output. We do not store submitted documents after the request completes and do not use them to train AI models.

We may keep limited operational records: the time of each request, document type, file size, result status, and payment details such as the network, transaction identifier, and paying wallet address. Payment details are also recorded publicly on the blockchain. See our Privacy Policy.

6. Acceptable Use

You agree not to:

  • submit unlawful content, malware, or documents you are not authorized to share;
  • attempt to obtain Output without paying, or to circumvent or interfere with payment;
  • overload, disrupt, probe, or attack the API or Subpay’s systems;
  • use the API to build a substantially similar competing service by harvesting its Output at scale; or
  • use the API in violation of any law, including sanctions and export laws.

We may limit request rates, and may block or refuse requests from any wallet, address, or client at our discretion, including to prevent abuse.

7. Availability and Changes

The API is provided without any service-level commitment. We may change, suspend, or discontinue the API, its output format, supported documents, networks, or price at any time, with or without notice.

8. Disclaimer of Warranties

THE API AND ALL OUTPUT ARE PROVIDED ON AN “AS IS” AND “AS AVAILABLE” BASIS. SUBPAY EXPRESSLY DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF ACCURACY, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE API WILL BE UNINTERRUPTED, SECURE, OR ERROR-FREE, OR THAT ANY OUTPUT WILL BE ACCURATE OR COMPLETE.

9. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, SUBPAY AND ITS OPERATORS SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS, REVENUES, FUNDS, DATA, OR GOODWILL, ARISING FROM YOUR USE OF OR RELIANCE ON THE API OR ANY OUTPUT, INCLUDING ANY PAYMENT, APPROVAL, OR FUNDING DECISION MADE USING OUTPUT.

OUR TOTAL LIABILITY FOR ALL CLAIMS RELATING TO THE API SHALL NOT EXCEED THE FEES YOU PAID FOR THE SPECIFIC READS GIVING RISE TO THE CLAIM.

10. Indemnification

You agree to indemnify, defend, and hold harmless Subpay, its affiliates, and its operators from and against any claims, liabilities, damages, losses, and expenses (including reasonable attorneys’ fees) arising out of or connected with your or your agent’s use of the API, your reliance on any Output, documents you submit, or your violation of these API Terms or any third-party right.

11. Governing Law

These API Terms shall be governed by and construed in accordance with the laws of the State of Florida, without regard to its conflict of law principles. Any legal action or proceeding arising under these API Terms will be brought exclusively in the state or federal courts located in Florida, and the parties irrevocably consent to the personal jurisdiction and venue therein.

12. Changes and Contact

We may update these API Terms at any time by posting a new version on this page. The version in effect when you send a request governs that request. Questions: support@subpay.ai.