pump.fun Developer API Terms

Last Updated: October 22, 2026

1. Introduction

1.1. These Developer API Terms (these “API Terms”) are a legally binding agreement between the person that applies for or uses the Developer API (“Developer”, “you” or “your”) and Baton Corporation, Ltd., a company incorporated in England and Wales with its registered office at 82a James Carter Road, Mildenhall, Bury St. Edmunds, England, IP28 7DE, acting for itself and on behalf of the other Pump Entities (“Pump”, “we”, “us” or “our”). They govern your access to and use of the Developer API, the Developer Console, the Documentation, the MCP Server, the SDK and any API Data (together, the “Developer Services”).

1.2. The Developer Services are provided in connection with the Pump Platform. The pump.fun Terms of Use published at https://pump.fun/docs/terms-and-conditions (the “Terms of Use”), the Privacy Notice published at https://pump.fun/docs/privacy-policy (the “Privacy Notice”) and the Trademark Guidelines published at https://pump.fun/docs/trademark-guidelines (the “Trademark Guidelines”), each as updated from time to time, are incorporated into these API Terms to the extent stated in Section 3. If these API Terms conflict with the Terms of Use in relation to the Developer Services, these API Terms prevail.

1.3. By submitting an application in the Developer Console, by indicating acceptance in the Developer Console (including each time you create or rotate an API Key), or by accessing or using any Developer Service, you accept these API Terms. If you do not agree to these API Terms, do not apply for, access or use the Developer Services.

1.4. If you use the Pump Platform in your own right, your use of the Pump Platform (including the pump.fun account through which you sign in to the Developer Console) continues to be governed by the Terms of Use.

2. Eligibility and Authority

2.1. To apply for or use the Developer Services you must be an individual who is at least 18 years of age and of the legal age of majority in your jurisdiction, or a company, partnership, foundation or other legal person or organisation, in each case with the full power, authority and capacity to enter into and perform these API Terms.

2.2. If you apply on behalf of a company or other organisation, the individual who submits the application, indicates acceptance or creates an API Key represents and warrants that he or she is at least 18 years of age and of the legal age of majority in his or her jurisdiction, and is duly authorised to act on behalf of and bind that organisation for the purposes of these API Terms. If that individual is not so authorised, that individual is personally bound by these API Terms as the Developer.

2.3. The eligibility criteria in Section 2 of the Terms of Use apply to the Developer and to each individual who accesses the Developer Services on its behalf. Without limiting those criteria, you may not apply for, access or use the Developer Services if you, or any person who Controls you, is located, incorporated, otherwise established in, resident of, or has business operations in a Prohibited Jurisdiction, or is a Sanctioned Person, and you may not use the Developer Services in or for the benefit of any person in a Prohibited Jurisdiction or any Sanctioned Person. We may use the information you provide, the IP address from which you accept these API Terms and any other information available to us to assess eligibility, and we may use technical measures to restrict access to the Developer Services from any jurisdiction.

2.4. You represent and warrant that the information you provide in your application and in the Developer Console (including the name under which you apply, your website, contact email and intended use) is accurate and complete, and you will keep it up to date. The contact email you verify in the Developer Console is the Developer’s address for notices under Section 20.

3. Relationship to the Terms of Use, the Privacy Notice and the Trademark Guidelines

3.1. The following provisions of the Terms of Use are incorporated into these API Terms and apply to the Developer Services as if set out in full, with references to “these Terms” read as references to these API Terms, references to the “Pump Platform” and “Pump Services” read as including the Developer Services, and references to “you” read as references to the Developer: Section 2 (Eligibility); Section 16 (Pump IP); Section 21 (Prohibited Use); Section 22 (Representations and Warranties); Section 23 (Technology Disclaimers); Section 25 (Liability), as modified by Section 17 of these API Terms; Section 26 (Governing Law); Section 27 (Dispute Resolution; Arbitration); Section 29 (General Terms); and Section 32 (Definitions and Interpretation) to the extent of terms used in these API Terms and not defined in Section 22.

3.2. Capitalised terms used but not defined in these API Terms have the meanings given in the Terms of Use or, for “Personal Data” and “Data Protection Law”, in the Privacy Notice. Where Section 27.11 of the Terms of Use refers to identifying your Wallet address in an opt-out notice, you must instead identify the Developer’s name and verified contact email as recorded in the Developer Console.

3.3. The Privacy Notice describes how we process Personal Data in connection with the Developer Services, including the information you provide in the Developer Console and records of your use of the Developer API. The Trademark Guidelines govern your use of the Pump Entities’ names, logos and other trade marks.

3.4. The Documentation, including the published limits, the versioning and deprecation policy and the API reference, forms part of these API Terms. Where these API Terms refer to limits, scopes or policies “shown in the Documentation or the Developer Console”, the version shown at the time of the relevant request applies.

4. The Developer Services

4.1. The Developer API. The Developer API is a keyed, read-only programmatic interface through which approved Developers may retrieve API Data. The Developer API does not act as a user of the Pump Platform: an API Key cannot create, post, follow, trade, transfer, sign or otherwise take any action on the Pump Platform, and does not provide access to any user’s private messages, settings, session or other non-public information.

4.2. API Data. “API Data” means the data, content and other material returned by the Developer API, which consists of User Materials and other information that is publicly available on the Pump Platform (such as public profiles, usernames, Wallet addresses, posts, replies and other User Materials, follow relationships, leaderboards and public group memberships), information derived from public blockchains (such as the positions, trades, balances and estimated portfolio values associated with a Wallet address), and Pump’s own computations, estimates and markers derived from that information. API Data does not include market or price data for Digital Assets except as incidentally contained in the foregoing.

4.3. The Developer Console. The Developer Console at https://developers.pump.fun is where you apply for access, accept these API Terms, create, name, rotate and revoke API Keys, view your own usage and manage your contact details. You sign in to the Developer Console through your pump.fun account. One Developer may be registered per pump.fun account, and only that account may manage the Developer.

4.4. Scopes. Each API Key carries one or more scopes that determine which families of API Data it may retrieve. The scopes available, the routes within each scope and the default scopes granted to a new API Key are shown in the Documentation and the Developer Console. We may grant, decline, add or remove scopes for any API Key at our discretion. Certain scopes, including the scope that returns whether a Wallet address is currently restricted from the Pump Platform (the “Moderation Scope”), are granted only on specific request and are subject to the additional conditions in Section 8.6.

4.5. The MCP Server. The MCP Server at https://mcp.pump.fun allows software agents, including artificial-intelligence agents, to call the Developer API using your API Key. The MCP Server is a pass-through to the Developer API: it holds no API Keys and no API Data of its own, every request made through it is made under, and counts against the limits of, the API Key supplied with the request, and the same scopes, limits, suspensions and revocations apply as for a direct request. Every request made through the MCP Server using your API Key, and everything an agent does with the API Data it receives, is your use of the Developer Services under these API Terms.

4.6. The SDK and Documentation. We may make available client libraries, code samples, API descriptions and other software and documentation for use with the Developer API (the “SDK” and the “Documentation”). Where any component of the SDK is distributed under its own licence terms, those terms govern your use of that component and prevail over Section 9 to the extent of any conflict; otherwise the SDK and Documentation are licensed to you under Section 9.

4.7. Private beta and other pre-release features. We may make some or all of the Developer Services available on an invitation-only, beta, preview or other pre-release basis. Pre-release features may be incomplete, may change or be withdrawn at any time, and are provided without any commitment as to their future availability or form.

5. Applications and Approval

5.1. To obtain access you must submit an application in the Developer Console, verify your contact email and request the scopes you need. We review each application. We may approve or decline any application, in whole or in part, at our sole discretion and without giving reasons, and we may limit applications to Developers we have invited.

5.2. Approval is personal to the Developer that applied and is not transferable. You may not apply on behalf of, or make the Developer Services available to, any other person except as permitted by Section 8.

6. API Keys and Security

6.1. Once approved you may create API Keys in the Developer Console, up to the number shown in the Developer Console. Each API Key is shown in full once, at creation, and is not stored by us in a recoverable form. Each time you create or rotate an API Key you must accept the then-current version of these API Terms.

6.2. API Keys are confidential credentials. You must keep each API Key secret, use it only in server-side software under your control, and never embed it in, or send it from, a web page, browser, mobile application, client-side code, public repository, URL or any other location from which it could be read by a third party. A request bearing an API Key that originates from a browser or other client-side environment is treated by us as evidence that the key has been exposed, and we may revoke that API Key without notice.

6.3. You are responsible for all activity under your API Keys, whether or not authorised by you, including activity by your employees, contractors, affiliates and software agents and activity resulting from an exposed key, until you revoke the key in the Developer Console or we do so. You must notify us at the Support Address immediately on becoming aware that an API Key has been or may have been exposed, and rotate or revoke it.

6.4. You may not share, sell, lease, sublicense or otherwise make an API Key available to any third party, use an API Key issued to another Developer, or attempt to obtain or use an API Key other than through the Developer Console.

7. Limits and Fair Use

7.1. Use of the Developer API is subject to rate limits, daily quotas, limits on the number of active API Keys and other limits shown in the Documentation and the Developer Console (“Limits”). Limits are applied per API Key unless otherwise stated. We may set, raise, lower or otherwise change the Limits applicable to any API Key, scope, route or Developer at any time and with immediate effect, including setting any Limit to zero, and a changed Limit applies from the moment it is shown in the Documentation or the Developer Console or signalled in the response headers of the Developer API, whichever is first.

7.2. You must honour the limit, remaining and reset headers and any retry-after instruction returned by the Developer API, and must not attempt to exceed or circumvent any Limit, including by distributing requests across multiple API Keys, Developers, accounts, source addresses or Developers acting in concert.

7.3. You must use the Developer API in a manner that does not place an unreasonable or disproportionate load on the Pump Platform or its infrastructure, as determined by us.

8. Licence to API Data and Permitted Use

8.1. Licence. Subject to your compliance with these API Terms, we grant you a limited, non-exclusive, non-transferable, non-sublicensable, revocable licence during the term of these API Terms to retrieve API Data through the Developer API within the scopes and Limits granted to you, and to use, reproduce and display that API Data within your own applications, websites, services, tools and research (your “Application”) for the purposes described in your approved application.

8.2. Ownership. As between you and us, the Pump Entities and their licensors own all rights in the Developer Services and the API Data, including Pump’s computations, estimates, markers and compilations of data, and User Materials remain subject to the rights of the users who created them. You obtain no rights in the Developer Services or the API Data other than the licence in Section 8.1. The Developer Services and the API Data are Pump IP for the purposes of the Terms of Use.

8.3. Prohibited uses of API Data. You must not, and must not permit any person to:

• a. sell, rent, lease, license, redistribute, syndicate or otherwise make the API Data, or any substantial part of it, available to third parties as a dataset, feed, database or similar product, or otherwise distribute API Data other than as displayed within your Application;

• b. use the Developer API or the API Data to build or offer a service that provides programmatic access to API Data, or that substitutes for or competes with the Developer API or the Pump Platform’s public data features;

• c. use API Data, alone or combined with any other information, to identify any person who is not already identified in the API Data, to associate a Wallet address with a natural person, to infer any person’s location, identity or characteristics, or to build a profile of any person, or otherwise to de-anonymise, re-identify or profile any user of the Pump Platform;

• d. use API Data to monitor, track, target, harass, intimidate, stalk, defame, discriminate against or cause harm to any person, or for surveillance of any kind;

• e. use API Data, or any output of the Developer API, to train, fine-tune, evaluate, ground, benchmark or otherwise develop any machine-learning, artificial-intelligence or large-language model, or to create embeddings, datasets or corpora for any such purpose; this does not prevent an agent from retrieving API Data through the MCP Server to answer a request at the time it is made, provided the API Data is not retained for any purpose described in this paragraph;

• f. systematically enumerate, crawl or bulk-retrieve API Data, including by iterating over Wallet addresses, user identifiers or usernames, other than as reasonably necessary to serve requests made by users of your Application;

• g. use API Data in a manner that violates Applicable Law, the Terms of Use, the Privacy Notice or any user’s rights, including intellectual-property, privacy, publicity and data-protection rights;

• h. use API Data in connection with any Transaction, service or activity in or for the benefit of a Prohibited Jurisdiction or a Sanctioned Person;

• i. remove, obscure or alter any attribution, notice or identifier contained in or accompanying the API Data; or

• j. use the Developer API, the MCP Server or the API Data for any purpose other than the purpose described in your approved application, without first updating your application in the Developer Console.

8.4. Positions and trading data. API Data that reports positions, trades, balances, profit and loss, cost basis, portfolio value or similar figures consists of Pump’s estimates derived from the transactions it indexes and the prices it sources. These figures are informational only, are not accounting, tax or financial records, may be incomplete or inaccurate, and must not be presented in your Application as anything other than estimates provided by pump.fun. You must not use such API Data, whether for a single Wallet address or in bulk, to profile, track or target any person, and you must not query Wallet addresses other than as reasonably necessary to serve requests made by users of your Application.

8.5. Third-party content and links. API Data may include or link to content hosted by third parties, including Digital Asset metadata and images hosted at addresses chosen by the creator of the Digital Asset and images and profile links from third-party social networks. We do not host, control, endorse or take responsibility for that content, which may be subject to its owner’s terms. You are solely responsible for your retrieval, display and use of third-party content.

8.6. Moderation Scope. If we grant you the Moderation Scope, you may use the information it returns solely to hide, exclude or de-rank Wallet addresses within your Application so that your Application is consistent with the Pump Platform. You must not display, publish or communicate to any person that a particular Wallet address or user is or has been restricted, banned or sanctioned by pump.fun, must not use that information for any other decision about or treatment of any person, and must not store it for longer than 24 hours. We may withdraw the Moderation Scope at any time.

8.7. Caching, deletions and takedowns. You may cache API Data only as reasonably necessary to operate your Application and for no longer than 24 hours from retrieval (the “Cache Window”), after which you must re-retrieve it from the Developer API or discard it. User Materials and other API Data may be removed from the Pump Platform at any time, including because a user deletes content or an account or because we restrict a user or Wallet address, and the Developer API will stop returning that API Data without notice to you. You must ensure that any API Data that is no longer returned by the Developer API is removed from your Application and your systems no later than the end of the Cache Window, and within 24 hours after we notify you that specific API Data is to be removed. Nothing in this Section 8.7 permits you to retain API Data for a purpose prohibited by Section 8.3.

8.8. Monitoring and audit. We may monitor your use of the Developer Services, and may require you to provide information about your Application and your use of API Data, to verify compliance with these API Terms. You must respond to any such request within ten (10) Business Days.

9. Licence to the SDK and Documentation; Feedback

9.1. Subject to your compliance with these API Terms, we grant you a limited, non-exclusive, non-transferable, non-sublicensable, revocable licence during the term of these API Terms to use, reproduce and modify the SDK and the Documentation solely to develop and operate your Application in accordance with these API Terms.

9.2. If you provide us with any suggestions, ideas, feedback or other input about the Developer Services (“Feedback”), you grant the Pump Entities a perpetual, irrevocable, worldwide, royalty-free, sublicensable licence to use and exploit the Feedback for any purpose without obligation to you.

10. Your Application and End Users

10.1. You are solely responsible for your Application, including its content, operation, security, legality and compliance with Applicable Law, and for the acts and omissions of its users (“End Users”). You must ensure that your Application and your End Users’ use of it comply with these API Terms, the Terms of Use and the Privacy Notice to the same extent as if your End Users were bound by them directly, and you must not permit any End User to do anything that you may not do under these API Terms.

10.2. You must not represent or imply that your Application is created, operated, endorsed, sponsored or certified by, or affiliated with, any Pump Entity or the Pump Platform, or that you have any status with the Pump Entities beyond that of a Developer using the Developer API under these API Terms. Any use of the names, logos or other trade marks of the Pump Entities must comply with the Trademark Guidelines.

10.3. Attribution. Wherever your Application displays API Data you must identify pump.fun as the source of that data in a manner reasonably prominent to End Users (for example “Data from pump.fun”), in accordance with any attribution requirements in the Documentation and the Trademark Guidelines.

10.4. Your Application must not be used for, and must not facilitate, any activity prohibited by Section 21 of the Terms of Use or Section 8.3 of these API Terms, and must not be marketed or made available in or to a Prohibited Jurisdiction or a Sanctioned Person.

10.5. You must publish and comply with a privacy notice for your Application that accurately describes your collection, use and disclosure of Personal Data, including API Data, and complies with Applicable Law.

11. Data Protection

11.1. API Data includes Personal Data relating to users of the Pump Platform. In retrieving, storing and using API Data you act as an independent controller (or the equivalent under Applicable Law) of that Personal Data and not as a processor on our behalf. You are solely responsible for determining and documenting a lawful basis for your processing of API Data, for providing any notices required by Data Protection Law, for honouring the rights of data subjects, for implementing appropriate security measures and for complying with all Data Protection Law applicable to your processing, including in respect of any transfer of API Data to another country.

11.2. Without limiting Section 8.3, you must not process API Data in a manner that is incompatible with the purposes for which users made the information public on the Pump Platform, must not combine API Data with other data in order to identify, profile or target any person, and must not process API Data for direct marketing to any person.

11.3. If we receive a request from a data subject, a Regulatory Authority or a court that relates to Personal Data you hold as a result of the Developer Services, you must give us reasonable assistance, and must give effect to any deletion or restriction we notify to you, within the time stated in Section 8.7 or such shorter time as Applicable Law requires.

11.4. You must notify us at the Support Address without undue delay, and in any event within 48 hours, after becoming aware of any unauthorised access to, or loss, disclosure or misuse of, API Data in your possession or control.

11.5. Our processing of Personal Data in connection with the Developer Services, including the Personal Data of the individuals who act for the Developer, is described in the Privacy Notice.

12. Fees

12.1. The Developer Services are currently provided without charge. We may introduce fees for some or all of the Developer Services, or for usage above stated Limits, at any time by publishing the fees in the Documentation or the Developer Console. Where we introduce or change a fee that would apply to you, we will notify you at your verified contact email or in the Developer Console before the fee takes effect, and your continued use of the fee-bearing Developer Service after that date is your agreement to pay the fee.

12.2. Any fees are stated and payable in the currency and by the means specified in the Documentation or the Developer Console, exclusive of taxes, and are non-refundable except as required by Applicable Law.

13. Changes to the Developer Services and to these API Terms

13.1. Changes to the Developer Services. We may change the Developer Services at any time. Changes that we consider additive (such as new routes, fields, parameters or error codes) may be made without notice. Changes that we consider breaking will be made in accordance with the versioning and deprecation policy published in the Documentation at https://docs.pump.fun/versioning-and-deprecation, as updated from time to time, under which a route affected by a breaking change continues to respond for the period stated in that policy after we announce the change. Our characterisation of a change as additive or breaking is final. You are responsible for monitoring the Documentation, the Developer Console and the response headers of the Developer API for changes.

13.2. Discontinuance. We may suspend, withdraw or discontinue the Developer Services, any Developer Service or any scope or route, in whole or in part, at any time, with such notice (if any) as we consider commercially reasonable in the circumstances. We have no liability to you or any End User for any change to, or suspension, withdrawal or discontinuance of, the Developer Services.

13.3. Changes to these API Terms. We may amend these API Terms at any time by publishing the amended API Terms in the Developer Console or at the address where these API Terms are published and updating the “Last Updated” date. Amendments take effect on publication, except that where an amendment materially reduces your rights we will notify you at your verified contact email or in the Developer Console before it takes effect. Your continued access to or use of the Developer Services after an amendment takes effect, and any acceptance you indicate in the Developer Console, constitute your agreement to the amended API Terms. If you do not agree to an amendment you must stop using the Developer Services and revoke your API Keys.

14. Suspension and Termination

14.1. Term. These API Terms take effect when you first accept them and continue until terminated in accordance with this Section 14.

14.2. By you. You may terminate these API Terms at any time by revoking all of your API Keys and ceasing to use the Developer Services, or by notifying us at the Support Address.

14.3. By us. We may suspend or terminate your access to the Developer Services, any Developer Service, any API Key or any scope, or suspend, restrict or terminate the Developer, at any time, with or without notice and with immediate effect, including where we believe that you or your Application has breached these API Terms, the Terms of Use or Applicable Law, poses a security, legal, regulatory or reputational risk to any Pump Entity or any user, has not used the Developer Services for an extended period, or where we are required to do so by Applicable Law or a Regulatory Authority, or where we discontinue the Developer Services under Section 13.2. We are not obliged to give reasons.

14.4. Effect. On termination of these API Terms, or on termination or revocation of any API Key or scope: all licences granted to you under these API Terms in respect of the terminated Developer Services end immediately; you must stop using the affected Developer Services; you must, within thirty (30) days, delete all API Data in your possession or control, other than aggregated and anonymised information derived from API Data that does not identify any user, Wallet address or User Materials and contains no API Data; and on our request you must confirm that deletion in writing. We may retain the records described in the Privacy Notice after termination.

14.5. Survival. Sections 1, 3, 8.2, 8.3, 8.4, 8.6, 8.7 (as to data retained in breach), 9.2, 10, 11, 14.4, 14.5 and 15 to 22, and any other provision which by its nature is intended to survive, survive termination of these API Terms.

15. Representations and Warranties

In addition to the representations and warranties incorporated by Section 3.1, you represent and warrant to the Pump Entities on each day on which you use the Developer Services that: (a) you have the power and authority to enter into and perform these API Terms; (b) your use of the Developer Services and your Application comply, and will comply, with these API Terms and Applicable Law; (c) you have obtained and will maintain all rights, consents and registrations necessary to operate your Application and to process API Data as you do; and (d) you are not, and no person who Controls you is, a Sanctioned Person or located in a Prohibited Jurisdiction.

16. Disclaimers

16.1. THE DEVELOPER SERVICES AND THE API DATA ARE PROVIDED “AS IS” AND “AS AVAILABLE”, WITHOUT WARRANTY OF ANY KIND. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE PUMP ENTITIES DISCLAIM ALL WARRANTIES, CONDITIONS AND REPRESENTATIONS, EXPRESS, IMPLIED OR STATUTORY, INCLUDING ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, COMPLETENESS, TIMELINESS, AVAILABILITY OR UNINTERRUPTED OR ERROR-FREE OPERATION.

16.2. We do not commit to any level of availability, latency, throughput or support for the Developer Services. The Developer Services run on the same infrastructure as the Pump Platform and may be paused, throttled or taken offline, in whole or in part, at any time. No service level agreement applies.

16.3. API Data is User Materials and other information made public by users of the Pump Platform, information derived from public blockchains and Pump’s estimates derived from them. The Pump Entities do not verify, endorse or take responsibility for API Data, which may be inaccurate, incomplete, out of date, unlawful, offensive or infringing. Nothing in the API Data is investment, financial, legal or tax advice or a recommendation or endorsement of any Digital Asset, user or Wallet.

16.4. Section 23 of the Terms of Use (Technology Disclaimers) applies to the Developer Services.

17. Limitation of Liability

17.1. Section 25 of the Terms of Use applies to these API Terms, except that, in place of any monetary cap stated in Section 25 of the Terms of Use, and to the maximum extent permitted by Applicable Law, the aggregate liability of the Pump Entities and their affiliates, officers, directors, employees, agents and licensors to you and your End Users, in contract, tort (including negligence), breach of statutory duty or otherwise, arising out of or in connection with these API Terms or the Developer Services shall not exceed one hundred United States dollars (US$100).

17.2. To the maximum extent permitted by Applicable Law, the Pump Entities shall have no liability for any loss of profits, revenue, business, goodwill, data or anticipated savings, for the cost of substitute services, for any change to or unavailability, suspension or discontinuance of the Developer Services, for any inaccuracy in or removal of API Data, or for any indirect, consequential, special, exemplary or punitive loss or damage, in each case however arising and even if foreseeable or advised of the possibility.

17.3. Nothing in these API Terms excludes or limits any liability that cannot be excluded or limited under Applicable Law.

18. Indemnity

You shall indemnify, defend and hold harmless the Pump Entities and their affiliates, officers, directors, employees, agents and licensors from and against all claims, demands, proceedings, losses, liabilities, damages, costs and expenses (including reasonable legal fees) arising out of or in connection with: (a) your Application, including its content, operation and availability and any End User’s use of it; (b) your or your End Users’ access to or use of the Developer Services or the API Data; (c) your processing of Personal Data contained in API Data, including any claim by a data subject or Regulatory Authority; (d) any breach of these API Terms, the Terms of Use or Applicable Law by you or any person acting under your API Keys; or (e) any claim that your Application or your use of API Data infringes or misappropriates the rights of any third party. Section 24 of the Terms of Use applies in addition to, and not in place of, this Section 18.

19. Governing Law and Dispute Resolution

These API Terms, and any Dispute arising out of or in connection with them or the Developer Services, are governed by the laws of the British Virgin Islands and are subject to the mandatory binding arbitration agreement and class action waiver in Section 27 of the Terms of Use, each as incorporated by Section 3.1. Dispute Notices under Section 27.2 of the Terms of Use must be sent to the addresses in Section 20.2.

20. Notices and Support

20.1. We may give you notice under these API Terms by email to the contact email you have verified in the Developer Console, by a message in the Developer Console, or by publication in the Documentation. Notice is effective when sent or published. You must keep your contact email current and monitor it and the Developer Console.

20.2. Formal legal notices to us (including Dispute Notices) must be sent by email to legal@pump.fun and by post to Baton Corporation, Ltd., 82a James Carter Road, Mildenhall, Bury St. Edmunds, England, IP28 7DE, marked for the attention of the Legal Department.

20.3. Questions about the Developer Services, reports of exposed API Keys and security notifications under Section 11.4 should be sent to developers@pump.fun (the “Support Address”). We may, but are not obliged to, respond to support requests.

21. General

21.1. Export and sanctions. You must comply with all applicable export-control and sanctions laws in connection with the Developer Services and must not export, re-export or provide the Developer Services, the SDK or the API Data to any Prohibited Jurisdiction or Sanctioned Person or for any prohibited end use.

21.2. Assignment. You may not assign, transfer, sublicense or delegate any of your rights or obligations under these API Terms without our prior written consent. We may assign or transfer these API Terms, in whole or in part, to any Pump Entity or to a successor to the relevant business without notice to you.

21.3. Entire agreement. These API Terms, together with the documents incorporated by Section 3, constitute the entire agreement between you and the Pump Entities in relation to the Developer Services and supersede all prior agreements, communications and understandings relating to their subject matter.

21.4. Third-party rights. Each Pump Entity may enforce these API Terms. Subject to that, no person other than the parties has any right to enforce any provision of these API Terms.

21.5. Section 29 of the Terms of Use (General Terms), including its provisions on severability, waiver, force majeure, language and interpretation, applies to these API Terms.

22. Definitions

In these API Terms, in addition to the terms defined above and in the Terms of Use:

“API Key” means a credential issued through the Developer Console that authenticates requests to the Developer API, together with any replacement issued on rotation.

“Business Day” means a day other than a Saturday, Sunday or public holiday in England.

“Control” has the meaning given in the Terms of Use, and “Controls” is construed accordingly.

“Developer API” means the programmatic interface made available by Pump at https://api.pump.fun and any successor address, including every version, route and scope of it.

“Developer Console” has the meaning given in Section 4.3.

“Documentation” means the documentation for the Developer Services published by Pump, currently at https://docs.pump.fun, including the API reference, the published Limits and the versioning and deprecation policy, as updated from time to time.

“MCP Server” has the meaning given in Section 4.5.

“Sanctioned Person” means any person that is the subject or target of sanctions administered or enforced by the United States of America, the United Kingdom, the European Union or the United Nations, or that is owned or controlled by, or acting on behalf of, any such person.

“SDK” has the meaning given in Section 4.6.

“Support Address” has the meaning given in Section 20.3.