LEGAL
Fix Kit Terms
Effective 2026-09-22 · Version 1
Defined terms used. From the Terms of Use: Discry, Operator, Site, Services, Scan, Directory, Index, Band, Fix Kit, Account, Machine Access. From the Refund Policy: Delivery Failure. From the API, MCP and Data License Terms: Badge. From the Privacy Policy: Controller. These Fix Kit Terms define four terms of their own:
- Order: one purchase of one Fix Kit for one API slug, placed through the checkout on the Site and identified by its purchase key (the identifier in your delivery link).
- Deliverables: the files that make up the Fix Kit bundle delivered for an Order, as described in section 4.
- Confirmation Scan: the single Discry-run re-scan of the API's public documentation surface that is included with an Order and described in section 10.
- Evidence: the public documentation, discovery files, and Scan results that Discry collected about the API before generation and that the Deliverables cite.
1. Who we are and what these terms cover
1.1. The Fix Kit is sold by Discry LLC, a New York limited liability company (the Operator), with its office at 418 Broadway, Suite 10855, Albany, NY 12207. The legal contact address is legal@discry.ai. The Site is https://discry.ai.
1.2. These Fix Kit Terms are the agreement between you and the Operator for every Order. They add to the Terms of Use, which continue to apply to the Site, your Account, and the Scan. These Fix Kit Terms prevail over the API, MCP and Data License Terms (for Machine Access), which prevail over the Terms of Use. The Privacy Policy, Cookie Policy, Crawler and Acceptable Use Policy, and Directory and Benchmark Policy are notices incorporated by the Terms of Use. The Refund Policy is incorporated by these Fix Kit Terms.
1.3. These terms cover only the Fix Kit. The repository product marked "In development" on the Site is not for sale and is not governed by them.
2. How you accept
2.1. You accept these Fix Kit Terms when you confirm the acceptance statement at the checkout step on the Site, which links to this document, and submit the Order for payment on the checkout page described in section 6.1. You also accept these terms by downloading the Deliverables. If you do not agree, do not submit the Order and do not download the Deliverables.
2.2. If you place an Order for an employer or another organisation, you confirm that you have authority to bind it, and "you" in these terms means that organisation as well as you personally.
2.3. The version of these terms in force when you submit the Order governs that Order, together with the versions of the Terms of Use and the Refund Policy in force on that day. Each Order records the price version in force at the time; the current price version is founding-119-v1.
3. Who can place an Order
3.1. You must hold an Account and have claimed the Scan for the API before you can place an Order. Claiming does not prove you control the domain, so section 13 asks you to confirm your authority.
3.2. An Order can be placed only for a Scan that has the status scored, has a comprehension result, and shows at least one failed or partial discovery check or at least one affected comprehension criterion.
3.3. A blocked, unreachable, or incomplete Scan is not eligible, and neither is a Scan with no failures, because there is nothing to fix. Where a Scan is not eligible, no Order is created and no payment is requested.
4. What you are buying
4.1. An Order buys one Fix Kit for one API slug at the price shown on the pricing page, which describes it as a one-time price. The Fix Kit is not a subscription, does not renew, and does not entitle you to any future edition of the Fix Kit or to any other product.
4.2. The Deliverables are a bundle of files. Every bundle contains at least one generated file or patch, together with fix-kit/README.md, fix-kit/IMPLEMENT.md, fix-kit/evidence/sources.md, fix-kit/evidence/scan-summary.json, fix-kit/tests/remediation-suite.json, fix-kit/tests/RUN.md, and fix-kit/manifest.json. A bundle with no generated file or patch is never delivered.
4.3. The manifest records the target API, the Scan provenance, the diagnoses, each change, the Evidence references, the remediation results, the Confirmation Scan entitlement, and a SHA-256 digest for every file and for the bundle, so you can check that the bundle you hold is the one Discry delivered.
4.4. At checkout you may ask for particular artifact types. A change you asked for that the measured failure does not require is labelled in the README and the manifest: "Customer-requested; not required by the measured failure; no predicted official score lift." Section 15.4 asks you not to remove that label when you show the Deliverables to others as Discry's output.
4.5. Every Order includes one Confirmation Scan that you may request within 90 days after delivery. Section 10 sets out how it works.
4.6. The Deliverables are the output of a large language model and may be wrong, so you must review them before use. Discry does not promise that they will change your score or Band or the behaviour of any agent; section 12 says this in full.
5. How the Deliverables are produced
5.1. The Deliverables are generated by a large language model through the Anthropic API from the public documentation of the API and the Evidence from your Scan. The prompt sent to Anthropic contains the API's slug, domain, category, documentation URL, GitHub organisation, and paradigm, the Scan provenance, the score summary, the failures, and candidate document URLs. It does not contain your email address, your name, or your Account identifier. Anthropic processes that prompt under its own terms; the Privacy Policy describes what Discry knows.
5.2. The generator is instructed to assert nothing that is not present in an Evidence block and to make every claim a verbatim quotation from a cited Evidence block. Where a required value has no Evidence it must emit a placeholder token of the form {{PLACEHOLDER:name}} rather than invent a value, and where the right place in your repository is unknown it must say so rather than invent a path. Placeholders are therefore expected in a correct Fix Kit and are yours to fill.
5.3. Before delivery, each remediation task in the bundle must be judged to pass by a second model review with at least one cited Evidence reference. A task that fails, or that passes with no Evidence reference, stops the kit from being delivered. The review is instructed not to calculate or predict a Discry score.
5.4. A separate check rejects any customer-visible output that contains a held-out token, a score prediction, an answer key, raw grading detail, or an internal error. It runs before review and again before delivery.
5.5. Validation allows one revision round. If the revised bundle fails again, the Order is a failed Order under section 9 and the charge is refunded in full.
5.6. Generation spend is capped at $5 per Order and $25 per day across all Orders, enforced before any call to Anthropic, and model output is capped in length. If a cap prevents generation, the result is a failed Order under section 9, not a partial kit.
5.7. IMPLEMENT.md instructs any coding agent that applies the kit never to merge, deploy, or change repository or service settings without your authorisation and never to invent product facts. That instruction binds the agent you run; it does not make Discry responsible for what your agent does.
6. Price, payment, and who processes it
6.1. Payment is processed by Sold through Link, LLC, an affiliate of Stripe, acting as merchant of record. Discry remains the seller of the Fix Kit. The checkout page, your receipt, and your card statement show the purchase as "Sold through Link", and the statement line reads LINK.COM* DISCRY. Your payment is also governed by the Sold through Link Terms at https://link.com/terms, which set out your relationship with Link. Discry never receives or stores your card number.
6.2. You are charged the price, plus any tax shown at checkout, when you submit the Order. Generation starts once the payment succeeds. The Deliverables are released to you only after they have been generated and have passed the validation in section 5.
6.3. If generation or validation fails, the full amount you paid, including tax, is refunded to your original payment method automatically. You do not need to ask. Link notifies you of the refund. When the credit appears depends on your bank, not Discry.
6.4. Checkout is idempotent for each purchase key, so submitting the same Order twice does not create two charges or two generations. Purchase state held on Discry's servers is authoritative; a parameter in a URL is never treated as proof of payment.
6.5. The price is displayed on the pricing page. The checkout page shows you the currency, which may be your local currency, the tax, and the total before you confirm, and it asks for your name and billing address because tax depends on them. Link emails you the receipt and invoice.
7. Taxes
7.1. The displayed price excludes sales tax, VAT, GST, and similar taxes. Sold through Link, LLC calculates, collects, and remits those taxes as merchant of record, and the tax shown at checkout is the tax you pay. You are responsible for any shortfall attributable to the address or tax status you supplied at checkout.
7.2. The Fix Kit is classified for tax purposes under a provisional code for electronic software documentation or user manuals, and that classification is under review. A change of classification does not change the price you paid on an Order already paid for.
8. Delivery
8.1. After checkout you return to your order page on the Site, which shows the Deliverables when they are ready. Its address is your delivery link. Discry does not email it to you unless you ask under section 8.3, so keep it. The bundle is fetched with a bearer token carried in the delivery link; a missing or wrong token returns "not found". Only the hash of the token is stored, so Discry cannot recover a lost token. Keep the link private: anyone who holds it can download the Deliverables.
8.2. Delivery goes through a function that releases a bundle only once its Order is ready. The generated files are stored as artifact records with their filenames, Evidence references, and a SHA-256 for each file.
8.3. You may ask Discry to send the delivery link to addresses you nominate; that send is rate limited per Order. You are responsible for the people you nominate and confirm that each expects the email.
8.4. Delivery is all or nothing. Discry does not deliver a partial Fix Kit; if a complete one cannot be delivered, the charge is refunded in full under section 9.
9. Failed Orders, Delivery Failure, and refunds
9.1. A failed Order is one for which the Deliverables are never generated, whether because validation failed twice, a cap in section 5.6 prevented generation, or generation failed for any other reason. On a failed Order the full charge is refunded automatically, as section 6.3 describes.
9.2. Any other refund of a Fix Kit charge is made under the Refund Policy, either by the Operator after a request or by Link under its own refund policy, which the Refund Policy §3.4 describes. These terms add no other refund regime.
9.3. The separate automated refund that applied to products no longer sold does not apply to an Order under these terms.
9.4. If you paid and the download is not available within 72 hours, that is a Delivery Failure under the Refund Policy §4.1, and you are entitled to a full refund on request.
10. The Confirmation Scan
10.1. The Confirmation Scan is a service, not a warranty. It is one Discry-run re-scan of the API's public documentation surface, requested by you after you have deployed changes, that produces a fresh report under the same instrument. It is included in the price.
10.2. You request the Confirmation Scan through the Fix Kit result page using the same delivery token, and you must confirm that you have deployed your changes before the request is accepted. The entitlement is one run per Order.
10.3. The window closes 90 days after the delivery time recorded for the Order. A later request is refused unless the run had already completed. The window is not extended, paused, or reset for any reason.
10.4. Confirmation Scans are picked up by a worker that runs every fifteen minutes; Discry does not promise a completion time. The Confirmation Scan reads whatever is publicly reachable when it runs. If your documentation has changed in ways the Deliverables did not anticipate, or is unreachable, it reports what it finds.
10.5. The Confirmation Scan is a Discry-run docs-surface scan and its result enters the Index like any other. Your API's published score and Band may change in either direction, and Discry does not withhold, adjust, or delay the result because you paid.
10.6. Nothing in the Deliverables predicts what the Confirmation Scan will show. The manifest records predictedOfficialLift: null, and no prediction of score improvement is ever asserted.
11. Independence of the score
11.1. Scoring is identical whether or not the graded party has paid. Buying a Fix Kit does not buy a score, a Band, a ranking, a listing, a removal, or a delay.
11.2. Only Discry-run docs-surface scans enter the Index. Your own runs of the remediation suite, and any scan you run against your product or environment, are never published as Discry results.
11.3. The Deliverables never contain, and the generator is forbidden to calculate or predict, an official Discry score.
12. AI-generated content notice and no guarantee of outcome
12.1. The Deliverables are produced by a large language model. They can be wrong. They can quote your documentation accurately and still propose a change that does not fit your product or repository. You must review every file and patch before you use it, and you are responsible for what you deploy.
12.2. Discry does not promise that implementing any change in the Deliverables will improve your score, move your Band, change your ranking, or alter how any AI agent, model, crawler, or tool behaves toward your API. The remediation suite checks the disclosed tasks against your updated documentation; it does not test agents you do not control.
12.3. Where the Deliverables contain a placeholder token, the value is missing on purpose because no Evidence supported it. Deploying a placeholder unfilled is a mistake you can see before you make it.
12.4. The model may produce the same or similar text for another buyer with similar failures; Discry does not promise that the Deliverables are unique.
13. Your confirmations
By placing an Order you confirm each of the following:
13.1. You own the API and its documentation, or you are authorised by the owner to obtain and implement changes to that documentation. A claimed Scan is not proof of this, so this confirmation is what Discry relies on.
13.2. The documentation Discry read for the Scan and the Evidence was publicly reachable and lawfully published by you or with your authority.
13.3. Any artifact you request and any content you deploy from the Deliverables will be used only for the documentation of the API named in the Order.
13.4. You will not use the Fix Kit, the Confirmation Scan, or any other part of the Services to generate content that is unlawful, that infringes another person's rights, or that Anthropic's Usage Policy forbids; that policy applies because Discry sends your Order's prompt to Anthropic. If Discry reasonably believes an Order would breach it, Discry may decline the Order and refund it in full.
13.5. You are not placing the Order for a competitor of the API's owner, and you are not placing it to obtain a benchmark result for an API you do not control.
13.6. You will indemnify Discry against any third-party claim, and the reasonable costs of defending it, that arises from a confirmation in section 13.1, 13.2, or 13.5 being untrue, except where you are a consumer and the law does not permit an indemnity of this kind.
14. Ownership and licence
14.1. Once you have paid for your Order, you own the Deliverables generated for your Order: the generated files and patches, and the README, implementation prompt, remediation suite, and manifest as compiled for your Order. You may use, copy, modify, publish, and deploy them without restriction other than sections 13 and 15, and you may give them to your employer, your contractors, and your coding agents. Discry claims no copyright in the generated text.
14.2. Discry keeps everything that is not the generated text for your Order: the scan instrument, the task bank, the grading logic, the prompts, the README and IMPLEMENT.md templates from which those files are compiled, the bundle and manifest formats, the validation checks, and the Discry name and marks. Nothing in an Order licenses any of these.
14.3. The Evidence is drawn from the API's public documentation and from Discry's Scan results. Where the Deliverables quote your documentation, the quoted text stays yours. Where the Evidence includes third-party material referenced from your documentation, Discry grants no rights in it and you are responsible for your use of it.
14.4. Discry may keep and use the Order's diagnosis categories, remediation results, generation cost, and validation outcome in aggregated or anonymised form to improve the Fix Kit, the instrument, and the published methodology, provided that the form used does not identify you, the person who placed the Order, the Order itself, or the API. The text of the Deliverables and any quotation of your documentation are excluded from that use, and your Account details and email address are never part of it. This does not narrow anything the Directory and Benchmark Policy says about the API's published score.
15. What you may not do with the Deliverables
15.1. You may not use the Deliverables, the Evidence, or the Confirmation Scan to discover, reconstruct, or probe the held-out verification task bank, the task-selection logic, the rotation schedule, or the accept-sets and citation quotes that Discry keeps private. You may not search the Deliverables for canary strings or optimise documentation to reproduce them.
15.2. You may not use the Deliverables to game any benchmark, rating, or evaluation, whether Discry's or anyone else's, by planting text meant for a grader rather than a reader, by seeding answers to known test prompts, or by any similar means.
15.3. You may not present the Deliverables, the Confirmation Scan, or any Badge as a certification, endorsement, or approval by Discry.
15.4. You may not remove the "Customer-requested" disclosure in section 4.4 when you show the Deliverables to a third party as Discry's output. You may remove it from files you deploy to your own documentation.
15.5. You may not resell the Deliverables as a product. Using them in a consultancy engagement for the API's owner, with the owner's authority, is not resale.
15.6. Discry may refuse a Confirmation Scan, without refund, and withhold future Orders from an Account that breaches this section or whose confirmations in section 13 prove untrue. That does not affect ownership of Deliverables already delivered.
16. Support
16.1. Discry answers questions about what a delivered file or patch says and why it was proposed, by email to legal@discry.ai, on a reasonable-effort basis with no promised response time.
16.2. Discry does not implement the Deliverables, review your pull requests, or test your deployment under these terms. The Confirmation Scan is the only post-delivery service an Order includes.
17. Disclaimer of warranties
17.1. Except as expressly stated in these terms, the Fix Kit, the Deliverables, the Evidence, and the Confirmation Scan are provided as they are. Discry disclaims every implied warranty, including merchantability, fitness for a particular purpose, non-infringement, and accuracy.
17.2. Discry does not warrant that the Deliverables are correct, complete, free of placeholders, or fit for any repository, that they will pass any review you apply, or that they will produce any result described in section 12.2.
17.3. Discry does not warrant that a Confirmation Scan will run at any particular time or produce any particular result.
17.4. If you are a consumer in the European Union, the United Kingdom, or a US state whose law does not permit a disclaimer above, that disclaimer applies only to the extent the law allows, and nothing in these terms removes a right you cannot waive.
18. Limitation of liability
18.1. Discry's total liability for all claims arising out of or relating to an Order, the Deliverables, the Evidence, or the Confirmation Scan, whether in contract, tort, statute, or otherwise, is limited to the greater of the amount paid for that Order and the price of the Order.
18.2. Discry is not liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, lost revenue, lost data, or the cost of substitute services, even if told they were possible. Discry is not liable for any loss caused by deploying a Deliverable without the review section 12.1 requires.
18.3. These limits do not apply to liability that cannot be limited by law, including liability for death or personal injury caused by negligence, fraud, gross negligence, wilful misconduct, or the non-waivable rights of consumers in section 17.4.
18.4. The Terms of Use carry the general limitation for the free surfaces of the Site. This section is the only limitation that applies to the paid Order, and the two do not add together.
19. Chargebacks and fraud
19.1. If you believe a charge was wrong, ask first under the Refund Policy, which states the address, the content of a request, and the timeline. Disputes about a Fix Kit charge are handled by Sold through Link, LLC as merchant of record, which may ask Discry for information and may refund the charge if Discry does not answer within 48 hours. A chargeback raised without that request, or after the Deliverables have been downloaded, is treated as a dispute of the Order rather than a cancellation of it.
19.2. If a chargeback is raised, Discry may decline, by hand, to run a Confirmation Scan requested for that Order while the chargeback is open (no automated hold exists), may give Sold through Link, LLC, Stripe, and the card network the Order, delivery, and download records, and may decline future Orders from the same Account. Ownership of Deliverables already delivered is not affected, but Discry may recover the amount paid from you if the chargeback succeeded on information you knew to be untrue.
19.3. Discry may refuse to deliver, and refund the charge in full, where it reasonably believes the Order is fraudulent, uses a card without the cardholder's authority, or breaches section 13.
20. Consumers in the European Union and the United Kingdom
20.1. The Fix Kit is digital content supplied without a tangible medium, and generation begins as soon as your payment succeeds. If you are a consumer in the European Union or the United Kingdom, you may withdraw from the Order within 14 days after the day you place it, for any reason, unless at checkout you expressly consented to delivery beginning at once and acknowledged that you lose the right to withdraw once delivery has begun. If you gave that consent, the withdrawal right ends when generation starts. If you did not give it, or the consent was not shown to you, you keep the full 14-day right. The Refund Policy §4.4 states the same rule and how to exercise it. Sold through Link, LLC may also grant a cooling-off refund under its own policy, and Discry accepts any refund it grants.
20.2. Email legal@discry.ai with the purchase key to withdraw. If we read your withdrawal before generation has started, we refund the full amount you paid. No automated process halts a running generation on an email. Generation usually starts within minutes of payment, so if it has already started, the Refund Policy §4.4 applies.
20.3. Nothing in these terms limits the rights an EU or UK consumer has under mandatory local law, including remedies for digital content that does not conform to the contract. Where these terms and those rights conflict, the rights control.
21. Term, termination, and survival
21.1. These terms apply to an Order from submission until the end of the Confirmation Scan window.
21.2. Discry may end an Order, and refund it in full, in the cases sections 13.4 and 19.3 describe, and otherwise only by a refund under the Refund Policy.
21.3. Sections 11, 12, 14, 15, 17, 18, 19, 22, and 23 survive delivery, the end of the Confirmation Scan window, and the closure of your Account.
22. Personal data and records
22.1. Discry is the Controller of the personal data it processes for an Order. Discry stores your email address in clear text on the Order's generation record, together with the hash of the delivery token, the Evidence envelope, the generation status, any internal failure detail, and the validated manifest. Discry may store each address you nominate under section 8.3. The Privacy Policy describes retention, your rights, and how to exercise them.
22.2. Generation cost records are keyed to the purchase key and hold no other personal data.
23. Disputes
23.1. Section 14 of the Terms of Use governs every dispute arising out of or relating to an Order, the Deliverables, or the Confirmation Scan, and applies here as if repeated in full.
24. Changes to these terms
24.1. A new version of these terms applies only to Orders submitted after its effective date; the version in force when you submitted an Order governs that Order. Every version is dated and numbered at the top of this page, and the previous version is kept unchanged in Discry's legal archive and is available on request to legal@discry.ai.
25. General
25.1. These Fix Kit Terms, the Refund Policy, and the Terms of Use are the entire agreement for an Order. No pricing page, email, or Deliverable adds a promise to them.
25.2. If a provision is found unenforceable, the rest of these terms continue and the provision is read as narrowly as needed.
25.3. Discry's failure to enforce a provision is not a waiver of it.
25.4. You may not assign an Order or these terms without Discry's written consent, except to a successor of the business that owns the API. Discry may assign them to a successor of its business.
25.5. Notices to Discry go to legal@discry.ai. Notices to you go to the email address on the Order.
25.6. Discry is not liable for a delay or failure caused by events outside its reasonable control, including outages at Stripe, Anthropic, Supabase, or Vercel; a failed Order so caused is handled under section 9.
25.7. Headings are for reading only.
Machine-readable mirror: /legal/fix-kit-terms.md