Automated Access and Agent Disclosure
Effective Date: October 15, 2026 Version: 1.0 Applies to: All Developers and partners who connect an automated program or agent to the Platform.
Article 1: Introduction and Scope
1.1 This document governs automated access to the Platform. A Developer or partner that connects a program that acts on the Platform without a person directing each act shall disclose the program, shall register it as the Company requires, and is liable for its acts as the Developer's own acts. Undisclosed automated access is a material breach.
1.2 This document governs third-party automated programs only. The Company's own automated services are governed by the documents for those services and are outside this document. If a provision of this document conflicts with the Terms of Use, this document controls for automated access. If a provision of this document conflicts with the Developer Agreement, this document controls for automated access and disclosure. Policies and help pages explain this document; they do not amend it.
Article 2: Definitions
2.1 In this document, terms defined in the Developer Agreement have the same meaning, and, in plain words Agent: a program that reads Platform state and takes an act on the Platform on its own, or with a person reviewing a group of acts rather than each act. An Agent includes a program that sets a price, creates or changes a listing, sends a message to a Buyer, places or divides an Order, or touches a payment.
Connection: a link between an outside automated system and Platform data, tools, or acts, by which the outside system can read Platform data or cause an act on the Platform.
Level of Control: one of the following, stated for each Agent: advisory, meaning the Agent recommends and a person acts; supervised, meaning the Agent acts and a person reviews each act or each group of acts; or uncontrolled, meaning the Agent acts without review of each act.
Operator: the Developer or partner responsible for an Agent or a Connection. Responsibility is not transferred by engaging a contractor to build the Agent; the Operator changes only if the contractor registers as the Operator.
Agent Act: an act that changes Platform state: writing a listing, changing a price, sending a Buyer message, placing or dividing an Order, or touching a payment.
Article 3: Registration Before Operation
3.1 No Agent shall take an Agent Act on the Platform, and no Connection shall touch Platform data or an act, until the Agent or Connection is registered and approved. An unregistered Agent cannot be distinguished from a program used to commit fraud, and unregistered operation is a material breach without a cure period under Article 9.
3.2 The registration shall state, completely and truthfully: (a) the Operator's identity: legal name, contact, and the Platform account the Agent acts under; (b) the capabilities: every Agent Act the Agent can take, listed one by one, so that a general phrase such as management of listings does not satisfy this clause; (c) the scope: the resources concerned, including each Seller account, each catalog item group, and each Buyer group; (d) the data access: each field and record the Agent reads, with an express statement where the Agent reads personal data, in which case the Data Use, Retention and Deletion applies in full; (e) the Level of Control for each capability, and, for an uncontrolled Agent, the limits that restrain it: a spending limit, an act-rate limit, and the stop control in Article 5; and (f) the system that provides the Agent's decision function: the provider, the name of the system, and where it runs.
3.3 The Company shall approve or deny a registration within ten (10) business days of a complete submission. Approval may impose a condition: supervised operation only for a stated period, a limit on the number or value of acts, a record of every Agent Act with its inputs, outputs, and decision-system version, or a restriction on hours of operation. A condition is part of the registration; breach of a condition is operation outside the registration.
3.4 Denial states the reasons. An Operator whose registration is denied may apply again after correcting the defects stated. A repeat submission that does not address the stated reasons may be rejected without review.
3.5 A material change requires a new registration before the changed Agent or Connection is put into operation: a new capability, a wider scope, a change of the decision system, a change of Level of Control, or a change of Operator. A change of version within the same decision-system family, with the same capabilities, is not material.
Article 4: Scope and Limits
4.1 Each Agent and Connection is limited to the smallest scope its function requires. The registration lists the permitted scope; an act outside the list is denied authority under this document. An Agent registered for one Seller that acts on another Seller's data operates without registration as to the second Seller.
4.2 An Agent acting for a Seller is bound by that Seller's own authority. A Seller cannot authorize an Agent to do an act the Seller cannot do: an Agent shall not reach another Seller's data, shall not use an internal interface, and shall not use a credential issued for internal or service use. Suspension of the Seller's access suspends the Agent's access at the same time.
4.3 An Agent that communicates with a Buyer shall state at the start of each exchange, in plain words, that the Buyer is communicating with an automated program. The statement shall not be hidden and shall not be worded to suggest a human correspondent. Impersonation of a human is prohibited, and an Agent shall answer truthfully when a Buyer asks whether the correspondent is automated.
4.4 Division of one Agent's work among many Agent identities to evade a rate limit, a registration duty, or an act limit is prohibited and is evasion under the Scraping Prohibition and the API Rate Limits and Quotas. The Company measures the Operator's total Agent activity, not the activity of each identity alone.
4.5 An Agent shall not use data the Agent collected in violation of the Data Use, Retention and Deletion, and shall not train a model on Platform data in violation of that document. An Agent has no wider data licence than the Developer behind the Agent.
4.6 An Agent shall not expand its own scope or capabilities without a new registration under clause 3.5. Expansion by the Agent itself is operation outside registration from the moment of expansion.
Article 5: Stopping an Agent
5.1 Each registration includes a stop control that takes effect within sixty (60) seconds of use. Three parties may use it: the Company, the Operator, and an affected Seller or Buyer through the Company. Use of the stop control means the Agent's credentials cease to operate and an Agent Act in progress is halted; filing of a request without the halt does not satisfy this clause.
5.2 The Company may stop an Agent on: conduct outside the registered pattern, including an act rate or an act pattern outside the registration; a breach of scope; involvement in an incident; or loss of the Operator's incident contact under the Partner Support and Incident Escalation Policy. Stopping under this clause is a protective measure that preserves the state for investigation. Repeated use of this clause against the same Operator is subject to review under Article 9.
5.3 A Connection with no traffic for ninety (90) days is treated as unused. The Company gives fifteen (15) days' notice and then ends the Connection, unless the Operator confirms a continuing need within the notice period.
5.4 The Operator's own stop control shall be tested before approval. At registration, the Operator demonstrates the stop control end to end in the Sandbox under the Sandbox Acceptable Use Policy: the Operator uses the control and shows that a later Agent Act fails. A stop control that has not been tested does not satisfy this document.
Article 6: Disclosure and Acknowledgement
6.1 A Seller that deploys an Agent touching a Buyer exchange, a listing, or a price shall acknowledge the disclosure for that feature before deployment. The disclosure states in plain language what the Agent does, what data the Agent touches, and that the Seller remains responsible for the Agent's acts. The acknowledgement is recorded with the Seller, the feature, and the time, as the audit record of who was informed of what, and when.
6.2 Acknowledgement is per Seller and per feature. Acknowledgement for a price Agent is not acknowledgement for a message Agent. A new acknowledgement is required when the disclosure wording changes in a material respect, judged from the Seller's position.
6.3 The Company maintains a record of each disclosure statement the Company issues about automated services, where the statement appears, and when the wording last changed, and makes that record available so that a Buyer or a Seller can determine what statement applied at a given time.
Article 7: Records and Incidents
7.1 The Operator shall record every Agent Act affecting a Buyer, a Seller, a listing, an Order, or a payment: the time, the Agent identity, the act taken, the inputs, the outputs, and the decision-system version. The Operator shall retain the record for twelve (12) months and shall produce it to the Company within five (5) business days of request.
7.2 An incident caused by an Agent: including a wrong Order, a wrong price, a misleading Buyer message, and a misdirected payment: shall be reported in accordance with the Breach Notification Requirements within twenty-four (24) hours.
7.3 On an incident, the Operator's first duty is containment: stop the Agent, determine the extent of the effect from the records clause 7.1 requires, and then report. Destruction of a record after an incident is concealment, is a material breach without a cure period under Article 9, and is a separate violation from the incident itself.
7.4 Liability for an Agent Act rests on the Operator and, where the Agent acts for a Seller, on the Seller for that Seller's obligations to a Buyer, in each case as the act of the responsible party. That an act was taken by a program is not a defence for the Operator or the Seller.
Article 8: Liability
8.1 Exclusion of certain damages. To the fullest extent permitted by law, neither party is liable to the other for indirect, incidental, special, punitive, or consequential damages, or for lost profits, lost revenue, or loss of goodwill, arising out of or relating to this document, even if the party has been advised of the possibility of those damages.
8.2 Cap. To the fullest extent permitted by law, the Company's total liability arising out of or relating to this document shall not exceed the greater of (a) the amounts the Developer paid to the Company under this document in the twelve months before the event giving rise to the claim, or (b) one hundred dollars ($100).
8.3 Carve-outs. This article does not limit (a) a party's indemnification obligations under this document; (b) liability for fraud or willful misconduct; (c) amounts the Developer owes for Orders, fees, chargebacks, or refunds under this document, including an amount arising from an Agent Act; or (d) liability that cannot be limited under applicable law.
8.4 Essential purpose. The parties agree that this article allocates risk between them, that it is an essential part of the basis of their bargain, and that it applies even if a limited remedy fails of its essential purpose.
Article 9: Indemnification
9.1 Duty. The Developer shall indemnify, defend, and hold harmless the Company and its members, managers, employees, and agents from and against every claim, demand, action, loss, liability, judgment, settlement, cost, and expense (including reasonable attorneys' fees) arising out of or relating to: (a) the Developer's breach of this document; (b) the Developer's Applications and Agents, including an Agent Act; (c) the Developer's violation of any law or of the rights of any person; and (d) taxes for which the Developer is responsible under this document.
9.2 Procedure. The Company shall give prompt written notice of a claim under this article. The Developer shall control the defense with counsel reasonably acceptable to the Company. The Company may participate in the defense at its own expense. The Developer shall not settle a claim in a manner that imposes any obligation or restriction on the Company, or that does not release the Company fully, without the Company's prior written consent.
9.3 Survival. This article survives the termination of this document.
Article 10: Enforcement and Appeals
10.1 Investigation. The Company may investigate any suspected violation of this document. The Developer shall cooperate with an investigation and shall produce the records this document requires the Developer to keep, including the Agent Act records in clause 7.1.
10.2 Notice. If the Company determines that the Developer has violated this document, the Company shall give written notice stating the provision violated and the facts relied on, except where notice would compromise an investigation of fraud, a safety risk, or a legal obligation.
10.3 Opportunity to cure. Where a violation is capable of cure, the Developer has ten (10) business days from notice to cure it and to confirm the cure in writing. No cure period applies to unregistered operation, to undisclosed automated access, to impersonation of a human, to evasion by division among Agent identities, to self-expansion of scope, to concealment of a record, to fraud, or to a violation that by its nature cannot be cured.
10.4 Measures. If a violation is established and is not cured within the period allowed, the Company may, proportionate to the violation: (a) issue a written warning; (b) stop an Agent or end a Connection under Article 5, and suspend or revoke the Credentials concerned; (c) suspend or remove an Application; (d) suspend the Account or a program participation, in whole or in part; (e) terminate this document and the Account; and (f) exercise any other right or remedy available under this document or at law. Immediate stopping and Credential revocation are available for a violation described in clause 10.3. Procedure is further governed by the Partner Suspension, Termination and Appeals.
10.5 Appeal. The Developer may appeal a measure under this article by written notice to legal@aapawz.com within thirty (30) days of the measure, stating the grounds and attaching the records relied on. The appeal is decided by a person who did not make the original decision. The Company's decision on appeal is final. A measure remains in effect during an appeal unless the Company directs otherwise in writing.
10.6 No waiver by delay. The Company's delay in acting on a violation is not a waiver of the violation or of any later violation of the same kind.
Article 11: Term and Termination
11.1 Term. This document takes effect when the Developer first connects an Agent or a Connection or registers under this document, whichever occurs first, and continues until terminated under this article or until the Developer Agreement terminates, whichever occurs first.
11.2 Termination by the Company. The Company may terminate this document on thirty (30) days' written notice for any reason, and immediately on written notice if the Developer materially breaches this document, engages in fraud, or becomes ineligible to participate.
11.3 Termination by the Developer. The Developer may terminate this document on thirty (30) days' written notice to support@aapawz.com, provided the Developer has no investigation outstanding and has stopped and deregistered every Agent and Connection.
11.4 Effect of termination. On termination: (a) every Agent registration and Connection ends and Credentials are revoked; (b) data obtained through an Agent or a Connection remains subject to the Data Use, Retention and Deletion; (c) obligations that arose before termination, including liability for a prior Agent Act, survive until satisfied; and (d) the Company shall pay amounts owed, less amounts the Company may set off under this document, within thirty (30) days, except amounts held in connection with an open investigation or dispute.
11.5 Survival. The Definitions, Liability, Indemnification, Enforcement and Appeals (for measures taken before termination), Dispute Resolution, and General Provisions articles survive termination, together with clause 7.1 for the period stated there.
Article 12: Dispute Resolution
12.1 Any dispute arising out of or relating to this document, or to the relationship it governs, is governed by the Dispute Resolution Policy, which is incorporated into this document by reference.
Article 13: General Provisions
13.1 Amendments. The Company may amend this document by posting the amended document in the Document Center and giving notice to the Developer at the email address in the Account. An amendment that materially increases the Developer's fees or obligations takes effect thirty (30) days after notice; other amendments take effect on posting. Continued use of the Platform after the effective date of an amendment is acceptance of it. If the Developer does not accept an amendment, the Developer's remedy is to terminate under Article 11 before the amendment takes effect.
13.2 Notices. Legal notices under this document shall be sent to legal@aapawz.com. Operational notices and all other communications shall be sent to support@aapawz.com. A notice to the Company is effective when the Company acknowledges receipt or, for email, one business day after sending, whichever is earlier. Notices to the Developer are effective when sent to the email address in the Account or posted to the Account's notice facility in the portal, whichever occurs first. The Developer shall keep the email address in the Account current. DMCA notices are given as provided in the DMCA and Copyright Policy, to the designated agent at legal@aapawz.com.
13.3 Governing law. This document is governed by the laws of the State of Tennessee, without regard to its conflict-of-laws rules. Subject to the Dispute Resolution Policy, any proceeding arising out of this document shall be brought in the state or federal courts located in Shelby County, Tennessee, and the parties consent to personal jurisdiction there.
13.4 Severability. If any provision of this document is held unenforceable, the provision shall be enforced to the fullest extent permitted, and the remaining provisions continue in full effect.
13.5 Entire agreement. This document, together with the documents it incorporates by reference, is the entire agreement between the Company and the Developer for the subject it governs and supersedes every prior or contemporaneous statement, communication, or agreement on that subject, whether written or oral.
13.6 Assignment. The Developer shall not assign this document or any right or obligation under it without the Company's prior written consent, and an assignment without consent is void. The Company may assign this document to an affiliate or in connection with a sale of all or part of its business, on notice to the Developer.
13.7 Waiver. A waiver of any provision of this document is effective only in writing and only for the instance stated. No waiver is a waiver of any other provision or instance.
13.8 Interpretation. Headings are for convenience only. "Including" means "including without limitation." This document shall not be construed against a party on the ground that the party prepared it. The English-language text controls over any translation.