Terms of Service
Wiredrag ApS
1. These terms, and who they apply to
These terms cover your use of Wiredrag, an API that reads a whole repository snapshot in one context and returns every place a named value is held, passed or stored, with what it confirmed, what it could not, and which files it did not read. They are a contract between Wiredrag ApS, of Havnegade 20, 8000 Aarhus C, Denmark (“Wiredrag”, “we”) and the company that signs up (“Customer”, “you”).
The service is for businesses only, not consumers. By signing up you confirm that you are acting for your business and that you have the authority to commit your company.
The person who accepts these terms accepts them for the company, not for themselves. If you don’t have that authority, please don’t go ahead.
If documents disagree. This order applies: (1) a signed order form or agreement between us, (2) the data processing agreement, (3) these terms, (4) our Privacy Policy, (5) anything else on our website.
2. What the service is
You send one repository at one commit, as a git archive or through a read-only GitHub or GitLab token scoped to that repository, and a question asking for every place a named value is held, passed, stored or parsed in a stated way. Before any charge we set aside by rule binaries, large data files, large vendored directories, generated output and files our parsers cannot parse, and tell you which and why, with the price of a question. We read the rest in one context with our long-context model, collect the answer directory by directory, and check every cited file and line with our parsers. You receive an answer listing each place with its file, its line, how the value is held there, the hops that led to it, the reason it was listed and a proposed change that is not applied, each marked found or unconfirmed, with a ledger of the files not read and the boundaries reached, as JSON and as a readable document. A re-ask against a later commit marks each place as changed, unchanged, new or gone since the last answer.
3. What the service is not
These limits are deliberate, and they are part of what you are buying. They are not defects.
Not a code change. The service answers and stops. It opens no pull request, writes no patch, edits no file and widens no field; every change on the list is made by your engineers.
Not a safety verdict. An answer says where a value is held and how. It does not say whether a place is a bug, whether a change is safe to deploy, or what systems outside the snapshot do with the value.
Not runtime analysis. The service reads source files at one commit. It does not run your code, watch production traffic, read your databases or follow a value resolved at runtime by reflection, configuration loaded at deploy time or a service in another repository; such places are listed as unconfirmed with the boundary named.
Not inside your network. The service runs only on cloud GPU capacity we control in Stockholm. There is no version that runs on your own machines or in your own network.
4. What you need to do, and why it matters
What you get from the service depends a lot on things only you control. Please read this section carefully, because sections 9 and 10 build on it.
Send the commit you mean. An answer describes the snapshot you sent and nothing else. Name the commit; a branch that moves after upload is not followed.
Exclude what must not leave. Remove secrets, credentials and fixtures holding personal data before you send a snapshot, or exclude their paths. Excluded paths are named as not read in every answer.
Write the question precisely. Name the value's source and the property you are asking about, for example the id column of the orders table and every place it is held as a 32-bit integer. An answer follows the question as written.
Read the unconfirmed places. Places listed as unconfirmed and files listed as not read are yours to check by hand. Nothing is listed as found unless its trace was checked, and nothing outside the snapshot is listed at all.
Keep keys and tokens narrow. Issue read-only tokens scoped to the one repository you are sending, revoke a key when its holder leaves, and set a monthly spending cap that suits your account.
Send only code you may send. You confirm that you have the right to send each snapshot for this purpose, including any third-party code inside it.
5. Getting started, and what is free
A new account's first question is free and needs no payment card. It reads a repository of your own up to the full 60-million-token ceiling and returns the same answer, ledger and included re-ask as a paid question.
Every key comes with a sandbox snapshot of a public open-source repository, which can be asked ten questions at no charge.
6. Fees
Per question. A question is charged by the size of the snapshot it reads, measured in tokens at upload and quoted before any question is sent: $50 for a snapshot of up to 10 million tokens, about one million lines, and $180 for up to 60 million tokens, about six million lines. Every question past the 20th in a calendar month on one account is 20% off. Prices are in US dollars and exclude VAT. Customers in Denmark are charged 25% Danish VAT; business customers elsewhere in the EU account for VAT under the reverse charge; customers outside the EU are not charged Danish VAT.
Re-asks. The first re-ask of a question, against a later snapshot within 90 days of its answer, is included in the question's price. Each later re-ask costs a quarter of a question's price at the size of the new snapshot: $12.50 or $45.
What is not charged. Keys, the sandbox, snapshot quotes, a snapshot refused for being over the ceiling, questions declined before reading because they ask for a judgment rather than places, questions canceled before their read starts, and questions that stop partway or are answered more than 60 minutes after they were sent. There are no seats, minimums or terms.
Spending cap and invoices. Each account has a monthly spending cap that the customer sets; a question that would take the month past it is refused before reading and not charged. Invoices are issued monthly with one line per question and re-ask and the tokens it read, payable by card or bank transfer within 30 days.
7. Delivery, availability and support
Answer time. An answer is returned within 60 minutes of its question being sent, for a snapshot under the ceiling. A question answered later than that, or one that stops partway, is not charged, and whatever was read and checked is returned marked incomplete, naming the parts it did not reach.
Capacity. Up to two questions per account run at once; further questions wait in the order sent. Planned maintenance is announced by email at least two working days ahead.
Availability. We run the service with reasonable care. We do not promise an availability percentage; the remedy for a late or stopped question is that it is not charged.
Support. Support is by email at [email protected]. We aim to reply within one business day. That is a target, not a guarantee.
8. Answers, re-asks and deletion
Versions. Every answer carries the commit it read, the tokens and files read, the reader model's version and the time it was returned. A re-ask produces a new answer and never overwrites the old one, and it says so when the reader's version has changed in between.
Correction. If you believe a place listed as found is wrong, or that a place the snapshot shows is missing, tell us within 90 days of the answer and name the question. We check within two working days, with access to that answer only if you grant it; if our reader or our checker was at fault, the question is credited in full.
Export and deletion. An answer can be downloaded at any time while it is kept, as JSON and as a readable document. Deleting an answer through the API removes it within an hour and returns a deletion notice with the time.
9. What we promise, and what we don’t
We promise to provide the service with reasonable skill and care, and that we have the right to provide it.
We do not promise that an answer lists every place a value is held. An answer states what it found and traced, what it could not confirm and why, and which files it did not read; a place in another repository, in a vendor's system, behind runtime behavior or in a file not read lies outside what any answer can list.
Beyond that we give no other warranty. As far as the law allows, we exclude all implied warranties, including merchantability, fitness for a particular purpose and non-infringement.
10. Liability
10.1 Neither of us limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else the law says can’t be limited.
10.2 Losses neither of us covers. Neither of us is liable for lost profit, revenue, expected savings, business, goodwill or reputation, or for any indirect or consequential loss, however it arises.
10.3 Specific exclusions. We are not liable for a failure at a place an answer listed as unconfirmed, or did not reach because it lay in a file not read, an excluded path, another repository, a vendor's service or runtime behavior; for a change your engineers made or did not make from an answer; for a question that did not ask what you meant; or for code you sent without the right to send it.
10.4 Cap. Our total liability to you in any 12-month period is limited to the fees you paid us in that period. The cap does not apply to liability for intent or gross negligence, which Danish law does not allow a contract to limit.
10.5 You accept that the limits in sections 9 and 10 are a fair way to share risk, given the price and your part under section 4, and that we could not offer the service at this price without them.
11. Confidentiality and data
Your snapshots, questions, answers and marks, and the fact that you asked any given question, are your confidential information. We use them only to answer your questions, disclose them to no one, and delete them on the schedule in the privacy policy.
How we handle personal data is set out in our Privacy Policy and in the data processing agreement between us, which forms part of these terms. If the DPA and these terms disagree about personal data, the DPA wins.
12. Who owns what
Your code remains yours, and so do your questions and answers. We receive a license to process a snapshot only for the questions asked of it and only until it is deleted.
The reader model, the parsers, the hand-checked question set and the answer format are ours. Answers are licensed to you for use inside your business without time limit: you may share them with your engineers, contractors and auditors and copy them into your own tickets and plans.
You may not use our name or logo in public, and we may not use yours, without written permission first.
13. How long this lasts, and how it ends
13.1 The contract starts when you sign up and runs until one of us ends it.
13.2 You can end it. Cancel at any time. It takes effect at the end of the current billing month, unless section 6 sets a minimum term.
13.3 We can end it. We can end it with 30 days’ notice. We can end it immediately if you seriously break these terms and don’t fix it within 14 days of being told, if you become insolvent, or if your use exposes us to legal risk.
13.4 What happens then. We stop delivering and stop billing. You keep everything already delivered to you, and your right to use it continues. We delete or return our working copies as the DPA says. Sections 9, 10, 11 and 12 continue to apply.
14. Changes to these terms
We may update these terms. A change that matters takes effect 30 days after we email you about it. If you don’t accept it, you can end the contract before then. Using the service after that date means you accept the change.
15. Contact
Wiredrag ApS, Havnegade 20, 8000 Aarhus C, Denmark
[email protected]