Finology Software API and MCP Terms of Service

Effective date: September 5, 2026. Version 1.0.

These API and MCP Terms of Service (the “Agreement”) are entered into between Finology LLC, an Idaho limited liability company doing business as Finology Software (“Finology”), and the individual or entity that accesses or uses the Service (“Customer”). Finology and Customer are each a “Party” and together the “Parties.”

By requesting an API key, subscribing to a paid tier, executing the Finology MCP package against Finology’s servers, or transmitting any request to the Service, Customer accepts this Agreement. An individual who accepts on behalf of an entity represents that they have authority to bind that entity, and “Customer” refers to the entity. If Customer does not agree to this Agreement, Customer must not access or use the Service.

The Finology Terms of Service and Privacy Policy published at finology.tech govern the Finology website and applications generally. To the extent of any conflict concerning programmatic access, this Agreement controls. A written agreement executed by both Parties controls over this Agreement to the extent of any conflict.

1. Definitions

1.1 “Service” means Finology’s programmatic access to its federal student loan calculation engine, comprising (a) the REST application programming interface available at api.finology.tech; (b) the Model Context Protocol server available at mcp.finology.tech, including any keyless endpoint; (c) the @finology/mcp-server software package, to the extent it transmits requests to Finology’s servers; (d) the issuance of Keys; and (e) the Documentation.

1.2 “Engine” means Finology’s proprietary calculation engine, including without limitation its formulas, algorithms, methodologies, eligibility logic, rule tables, rules ledger, reference data, constants, tool definitions, prompts and descriptions, response structures, and provenance framework, in every form and version, together with all improvements and derivatives.

1.3 “Documentation” means the materials Finology publishes describing the Service, including the pages at finology.tech/agents, finology.tech/auth.md, and finology.tech/endpoints.md, the machine-readable discovery files under finology.tech/.well-known, and the descriptions embedded in the Service’s tools and responses.

1.4 “Key” means any credential Finology issues for access to the Service, including a sandbox key and a production key.

1.5 “Input” means the loan, income, household, and scenario figures Customer transmits to the Service.

1.6 “Output” means the figures, provenance data, citations, and related content the Service returns in response to an Input.

1.7 “Recorded Output” means an Output returned through an endpoint or tool that requires a Key. Outputs returned through a keyless endpoint or the local package are not Recorded Outputs.

1.8 “Agent” means any automated system, including a large language model or software agent, that Customer operates or permits to transmit requests to the Service or to relay Outputs.

2. License Grant

2.1 Subject to Customer’s continuing compliance with this Agreement, Finology grants Customer a limited, non-exclusive, non-transferable, non-sublicensable, revocable license during the Term to (a) transmit Inputs to the Service through the interfaces described in the Documentation; and (b) use, reproduce, display, and distribute Outputs, including within Customer’s own products and services and to Customer’s own users, in each case in the manner and subject to the conditions set out in this Agreement.

2.2 The @finology/mcp-server package is made available under the MIT License, which governs the package’s source code. That license does not extend to the Service, the Engine, or any Output, and requests the package transmits to Finology’s servers are use of the Service governed by this Agreement.

2.3 All rights not expressly granted in this Agreement are reserved to Finology. No license or right is granted by implication, estoppel, or otherwise.

3. Restrictions

3.1 Customer shall not, and shall not permit any Agent, employee, contractor, affiliate, or third party to, directly or indirectly:

(a) reverse engineer, decompile, disassemble, or otherwise attempt to derive, reconstruct, approximate, or replicate the Engine or any part of it, whether from the Service, the Documentation, or any collection of Outputs, except to the limited extent applicable law expressly prohibits this restriction;

(b) use the Service, the Documentation, or any Output to train, fine-tune, evaluate, calibrate, distill, or otherwise develop or improve any machine learning model, dataset, or automated system that is intended to reproduce, in whole or in part, the functionality of the Engine, or to develop or operate any product or service that competes with the Service;

(c) systematically extract, harvest, aggregate, or store Outputs for the purpose of assembling a dataset, table, or resource that substitutes for the Service or reduces reliance on it;

(d) copy, adapt, or incorporate the Documentation, the Service’s tool definitions and descriptions, or its provenance text into any other product or service;

(e) sell, resell, rent, lease, lend, sublicense, or otherwise make the Service or any Key available to any third party, share a Key across more than one organisation, or operate any service whose principal function is to provide access to the Engine under another name;

(f) circumvent, disable, or interfere with any Key requirement, quota, rate limit, security measure, or other technical control of the Service, including by rotating Keys, email addresses, or network addresses to obtain access beyond that allocated to a single Customer;

(g) remove, obscure, or alter any provenance data, attribution, rule version, “as of” date, or “estimated” designation carried by an Output, or present an altered figure as an Output of the Service;

(h) probe, scan, or test the vulnerability of the Service, or interfere with its operation or with any other customer’s use, other than through ordinary use of the documented interfaces; or

(i) use the Service in violation of applicable law or to harm, harass, defraud, or deceive any person.

3.2 Nothing in this Section 3 prohibits Customer from incorporating Outputs into Customer’s own products, or from publishing tests, comparisons, or benchmarks involving the Service, provided that any published figure is attributed to Finology Software and identifies the rule version and “as of” date carried by the Output.

4. Proprietary Rights

4.1 As between the Parties, Finology exclusively owns and retains all right, title, and interest in and to the Service, the Engine, the Documentation, and all related intellectual property rights, including all copyrights, trade secrets, trademarks, and patent rights, and including all suggestions, enhancement requests, feedback, and other information Customer provides relating to the Service, which Finology may use without restriction or obligation.

4.2 Customer acknowledges that the Engine constitutes valuable trade secrets and confidential information of Finology, developed at substantial expense; that the restrictions in Section 3 are reasonable and necessary to protect Finology’s legitimate interests; and that Customer’s access to the Service does not confer any ownership interest in the Engine or any Output structure.

4.3 As between the Parties, Customer owns its Inputs. Customer grants Finology a non-exclusive, perpetual, irrevocable license to process, store, and use Inputs and Outputs as described in Section 7.

5. Enforcement and Equitable Relief

5.1 Customer acknowledges that any actual or threatened breach of Section 3 or Section 4 would cause Finology immediate and irreparable harm for which monetary damages would be an inadequate remedy. Accordingly, in addition to any other remedy available at law or in equity, Finology shall be entitled to injunctive relief, specific performance, and other equitable relief to prevent or restrain any such breach, without the necessity of proving actual damages or posting a bond or other security.

5.2 Upon any breach of Section 3 or Section 4, Finology may immediately suspend or terminate Customer’s Keys and access to the Service without notice and without refund of any prepaid fees, and may pursue all remedies available to it, including under the Defend Trade Secrets Act, 18 U.S.C. § 1836 et seq., the Idaho Trade Secrets Act, Idaho Code § 48-801 et seq., and the Copyright Act. In any action arising from a breach of Section 3 or Section 4, Finology shall be entitled to recover its reasonable attorneys’ fees and costs, together with any profits or other benefits obtained by Customer or any third party as a result of the breach.

5.3 Finology maintains a record of each request made with a Key, including the endpoint or tool invoked, the time, the Key identifier, the rule version applied, and a hash of the Input. Customer acknowledges that Finology may rely on such records in any proceeding relating to this Agreement.

6. Keys, Access Tiers, Fees, and Payment

6.1 Keyless access. Finology may make certain functionality available without a Key. Outputs obtained without a Key are not Recorded Outputs, are subject to rate limits, and are provided without any commitment as to availability. Finology may modify, limit, or discontinue keyless access at any time without notice.

6.2 Sandbox Keys. A sandbox Key is issued automatically to the email address Customer supplies. It is limited to 100 requests per calendar month, expires 30 days after issuance, and may be revoked by Finology at any time. Issuance of a further sandbox Key to the same email address revokes the prior Key. The email address is recorded as supplied and is not verified.

6.3 Production Keys. A production Key is issued upon commencement of a paid subscription and remains valid while the subscription is in good standing. The production tier includes the monthly request allocation stated at the time of purchase, which is 100,000 requests per calendar month as of the Effective Date.

6.4 Quotas and rate limits. A single Key is valid for both the REST interface and the MCP server, and requests made through either count against the same monthly allocation. Allocations reset on the first day of each calendar month (UTC) and do not carry over. Requests exceeding the allocation, or exceeding the Service’s rate limits, are refused with HTTP status 429 and are not counted.

6.5 Fees. Customer shall pay the fees for the production tier at the price displayed at the time of subscription, which is US $499 per month as of the Effective Date. Fees are billed monthly in advance through Finology’s payment processor, Stripe, and are exclusive of any applicable taxes, which Customer shall bear. Subscriptions renew automatically each month until cancelled.

6.6 Cancellation and non-payment. Customer may cancel a subscription at any time through the billing portal identified in the Documentation. Cancellation takes effect at the end of the then-current billing period, at which time the associated Key is revoked. Fees are non-refundable, and no refund or credit is provided for partial periods. If a renewal payment fails, access continues during the payment processor’s retry period; if payment is not received by the end of that period, the subscription terminates and the Key is revoked.

6.7 Changes to fees and allocations. Finology may modify the fees or allocations applicable to paid tiers upon not less than 30 days’ notice to the email address associated with the subscription, effective at the first renewal following the notice period.

6.8 Key security. A Key is displayed once at issuance and is stored by Finology only in hashed form; Finology cannot recover or reissue a Key. Customer is solely responsible for maintaining the confidentiality of its Keys and for all activity conducted under them, whether or not authorised by Customer. Customer shall notify Finology at support@finology.tech promptly upon becoming aware of any unauthorised use or disclosure of a Key.

7. Data

7.1 Prohibited data. The Service is designed to receive loan, income, and household figures only. Customer shall not transmit to the Service, in any field, any information that identifies or could reasonably be used to identify a natural person, including names, Social Security numbers, dates of birth, account or loan numbers, addresses, telephone numbers, or email addresses. Customer bears sole responsibility for any such information transmitted in breach of this Section, and Finology may delete affected records without liability.

7.2 Records retained. Finology retains, for each Recorded Output, the record described in Section 5.3 together with the Output returned, and retains operational logs for all requests. Finology retains the contact and billing information necessary to administer subscriptions; payment card information is held by the payment processor and not by Finology.

7.3 Use of records. Finology uses the foregoing records to operate, secure, meter, and bill the Service, to substantiate the Outputs it has returned, to enforce this Agreement, and to compile aggregate statistics that do not identify Customer. Finology does not sell such records and does not use Inputs or Outputs to train machine learning models.

7.4 Privacy Policy. Finology’s Privacy Policy describes its handling of the personal information it holds concerning Customer’s account.

8. Nature of Outputs; Customer Responsibilities

8.1 Each Output is computed by the Engine from the Input supplied, by application of the federal repayment rules identified by the rule version and “as of” date stated in the Output, using constants for which the Output cites primary sources. No figure in an Output is generated or altered by a language model. Each Recorded Output is recorded in accordance with Section 5.3 before it is returned. Certain components of an Output, including estimated tax on forgiven balances, are estimates and are identified as such within the Output.

8.2 Outputs are provided for informational, educational, and planning purposes only. They do not constitute financial, tax, legal, accounting, or investment advice, and they are not a representation as to the action any lender, loan servicer, or governmental agency will take. Finology is not a lender, loan servicer, tax adviser, or financial planner, and no advisory or fiduciary relationship arises between Finology and Customer or any user of Customer’s products.

8.3 Where Customer presents any Output, or any figure derived from an Output, to any third party, whether directly, in a document, or through an Agent, Customer shall (a) present it as an estimate and not as advice; (b) preserve the “as of” date and any “estimated” designation carried by the Output; (c) not present a figure obtained without a Key as recorded, verified, or warranted; and (d) where the figure is published, attribute it to Finology Software and identify the rule version carried by the Output.

8.4 Customer is solely responsible for its Agents, for the manner in which Agents relay Outputs, and for compliance with all laws, regulations, and professional obligations applicable to Customer’s use of Outputs, including any obligation that applies when an automated system presents financial estimates to consumers.

9. Availability, Modifications, and Support

9.1 Finology provides the Service on a self-service basis and does not commit to any level of availability. Finology may suspend the Service for maintenance and will endeavour to provide advance notice of planned interruptions.

9.2 Finology may modify the Service at any time. Finology will provide not less than 30 days’ notice to the email address associated with a paid subscription before removing or materially changing a versioned endpoint, tool, or response field in a manner that would prevent a conforming client from operating. Changes to the federal rules the Engine applies, and consequent changes in Outputs, do not constitute modifications of the Service for this purpose.

9.3 Support is provided by email at support@finology.tech. Finology does not provide telephone support, meetings, or committed response times for self-service subscriptions.

9.4 Finology may suspend any Key immediately if Finology reasonably believes that the Key is compromised, that its use threatens the integrity or availability of the Service, or that it is being used in breach of this Agreement, or where suspension is required by law.

10. Disclaimer of Warranties

10.1 EXCEPT AS EXPRESSLY SET OUT IN SECTION 8.1, THE SERVICE, THE DOCUMENTATION, AND ALL OUTPUTS ARE PROVIDED “AS IS” AND “AS AVAILABLE,” AND FINOLOGY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, OR ARISING FROM COURSE OF DEALING OR USAGE OF TRADE. WITHOUT LIMITING THE FOREGOING, FINOLOGY DOES NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE, THAT ANY OUTPUT IS CORRECT, COMPLETE, OR SUITABLE FOR ANY DECISION, OR THAT ANY LENDER, LOAN SERVICER, OR GOVERNMENTAL AGENCY WILL ACT IN ACCORDANCE WITH ANY OUTPUT.

11. Limitation of Liability

11.1 TO THE FULLEST EXTENT PERMITTED BY LAW, IN NO EVENT SHALL FINOLOGY BE LIABLE UNDER OR IN CONNECTION WITH THIS AGREEMENT OR THE SERVICE, UNDER ANY THEORY OF LIABILITY, FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, BUSINESS, GOODWILL, OR DATA, EVEN IF FINOLOGY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

11.2 TO THE FULLEST EXTENT PERMITTED BY LAW, FINOLOGY’S AGGREGATE LIABILITY UNDER OR IN CONNECTION WITH THIS AGREEMENT OR THE SERVICE SHALL NOT EXCEED THE FEES PAID BY CUSTOMER TO FINOLOGY FOR THE SERVICE DURING THE TWELVE MONTHS IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM, OR ONE HUNDRED UNITED STATES DOLLARS (US $100) IF NO FEES HAVE BEEN PAID.

11.3 The limitations in this Section 11 apply notwithstanding the failure of essential purpose of any limited remedy. Where applicable law does not permit a limitation in this Section, that limitation applies to the fullest extent permitted.

12. Indemnification

Customer shall defend, indemnify, and hold harmless Finology and its members, managers, officers, contractors, and agents from and against any and all claims, demands, losses, liabilities, damages, costs, and expenses, including reasonable attorneys’ fees, arising out of or relating to (a) Customer’s or any Agent’s use of the Service; (b) any Output or derived figure that Customer or any Agent presents to any third party; (c) any information transmitted to the Service in breach of Section 7.1; or (d) any breach of this Agreement by Customer or any person acting under Customer’s Keys.

13. Term and Termination

13.1 This Agreement commences upon Customer’s acceptance and continues until terminated in accordance with this Section (the “Term”).

13.2 Customer may terminate this Agreement at any time by cancelling any subscription and ceasing all use of the Service.

13.3 Finology may terminate this Agreement (a) for convenience upon 30 days’ notice; (b) immediately upon notice if Customer fails to cure any breach within 10 days after notice of the breach; or (c) immediately and without notice upon any breach of Section 3, Section 4, or Section 7.1.

13.4 Upon termination, all Keys are revoked and all licenses granted under this Agreement cease. Sections 3, 4, 5, 7.2, 7.3, 8.2 through 8.4, 10, 11, 12, 13.4, and 14 survive termination.

14. General Provisions

14.1 Governing law and venue. This Agreement is governed by the laws of the State of Idaho, without regard to its conflict of laws principles. The Parties irrevocably submit to the exclusive jurisdiction and venue of the state and federal courts located in Idaho for any action arising out of or relating to this Agreement or the Service, save that Finology may seek injunctive relief in any court of competent jurisdiction.

14.2 Limitation period. Any claim arising out of or relating to this Agreement or the Service must be commenced within one year after the cause of action accrues, failing which it is permanently barred.

14.3 Amendment. Finology may amend this Agreement from time to time. Finology will provide not less than 30 days’ notice of any material amendment to the email address associated with a paid subscription and will update the version and effective date shown above. Customer’s continued use of the Service after the effective date of an amendment constitutes acceptance of it.

14.4 Notices. Notices to Finology shall be sent to support@finology.tech. Notices to Customer shall be sent to the email address associated with Customer’s subscription or Key request and are deemed received when sent.

14.5 Assignment. Customer may not assign or transfer this Agreement, by operation of law or otherwise, without Finology’s prior written consent. Finology may assign this Agreement without restriction, including in connection with a merger, acquisition, or sale of all or substantially all of its assets.

14.6 Entire agreement. This Agreement, together with the Documentation and the applicable subscription record, constitutes the entire agreement between the Parties concerning the Service and supersedes all prior or contemporaneous understandings.

14.7 Severability; waiver. If any provision of this Agreement is held unenforceable, it shall be enforced to the maximum extent permissible and the remaining provisions shall remain in full force. No waiver is effective unless in writing, and no failure or delay in exercising any right operates as a waiver of it.

14.8 Relationship of the Parties; no third-party beneficiaries. The Parties are independent contractors. Nothing in this Agreement creates a partnership, joint venture, agency, or employment relationship. No user of Customer’s products or other third party has any right under this Agreement.

14.9 Force majeure. Finology is not liable for any failure or delay caused by circumstances beyond its reasonable control.

Questions concerning this Agreement may be directed to support@finology.tech.