Agreement
These terms apply to techagents.online and everything published on it. Using the site means you accept them. If you do not, the remedy is simple and costs nothing: stop using the site.
Tech Agents publishes this site and is referred to below as “we”. You are referred to as “you”.
What this site is
Tech Agents is an editorial technology publication. It is free to read, requires no account, and is funded — where it is funded at all — by clearly labelled sponsorship described on the advertising page. It is not a support channel, a consultancy, or a service you have bought.
Who owns the content
Articles, comparisons, glossary entries, tool assessments, editorial illustrations and the design of the site are our copyright, except where a page says otherwise. The name Tech Agents, the wordmark and the agent-node logo are ours.
Facts are not owned by anyone. Nothing here stops you from writing about the same protocol, the same release or the same trade-off in your own words.
What you may do with it
You are welcome to do all of the following without asking us first:
- Read, print and save anything here for your own use, or to circulate inside your team.
- Quote a reasonable extract — a paragraph or two, or a table row — in an article, a talk, a newsletter or a thread, provided you name Tech Agents and link to the page you took it from.
- Link to anything, from anywhere, without permission and without a nofollow. Deep links to individual articles are fine and encouraged.
- Subscribe to the feeds — RSS, Atom or JSON Feed — to read the publication in a feed reader or to notify a team channel of new posts. All three carry the full text of each article, so you never have to come back here to finish one. Full text in a feed is a convenience for reading it, not a licence to republish it; the limits below still apply.
- Cite us as a source in academic or professional work, with a normal citation.
Code samples
Code in fenced blocks in articles and tutorials is there to be used. Unless a specific snippet says otherwise, you may copy, modify and ship it in your own projects — commercial or otherwise — with no attribution required and no licence to track.
The samples are teaching material: they illustrate a mechanism, and they are written to be short enough to read rather than hardened enough to deploy unchanged. Review, test and adapt them before they touch anything that matters. They are provided without warranty, exactly like the rest of the site.
What you may not do
- Republish articles in full, on your own site, in a newsletter, or as a syndicated feed, without written permission. A summary plus a link is always fine; a copy is not.
- Bulk-extract the site — automated scraping of the whole corpus, or of the search index, in order to reconstitute it elsewhere or to package it as a dataset or a product.
- Strip the byline or present our work as your own, or as machine-generated content of your own making.
- Use the name or the mark in a way that implies we endorse, reviewed or partnered with you when we did not.
- Attack the site — probing for vulnerabilities without invitation, hammering the endpoints, or interfering with anyone else's use of it. If you find a genuine security problem, the desk wants to hear about it; the address is on the contact page.
Polite crawling by search engines, feed readers and AI answer engines is expressly permitted, and robots.txt names every crawler the site recognises along with the paths that are closed to all of them.
Two machine-readable summaries of the publication are published on purpose: /llms.txt, an index of everything here, and /llms-full.txt, the same corpus with the text inlined. They exist so that a model answering a question about this subject can read what was actually written rather than reconstruct it from second-hand summaries. Fetching and reading them is fine, and so is quoting from them under the terms above — with attribution to Tech Agents and a link to the page the passage came from. What is not fine is the same thing that is not fine anywhere else on this site: repackaging the corpus as your own publication, your own dataset or your own product.
Tips, corrections and submissions
When you send us a tip, a correction, a tool submission or feedback, you keep whatever rights you already had in it, and you give us permission to read it, act on it and — where it is relevant — to quote it in coverage. We will not publish your name or your email address without asking you first.
Anything you send is treated as non-confidential unless you say otherwise before sending it, so mark embargoed or sensitive material clearly and in the first line. We cannot pay for unsolicited submissions and cannot promise to use or reply to them.
Newsletter
Subscribing is voluntary and unsubscribing is one click, from any issue. We may change the cadence or the format of the brief, or stop sending it. What we hold against your address, and what we do not, is set out in the privacy policy.
External links
Articles link out to documentation, specifications, repositories and vendor sites. Those destinations are not ours. We do not control their content, their availability, their security or their terms, and a link is not an endorsement of the linked organisation — often it is the opposite, and the link is there so you can check a claim for yourself. Follow external links at your own risk.
Third-party names and marks
Product, company and project names used on this site belong to their respective owners and are used descriptively — to identify what is being written about. Their use here is not a claim of affiliation, sponsorship or endorsement in either direction.
Not professional advice
Everything published here is informational and educational. It is not professional, legal, financial, security or engineering advice for your situation, and reading it does not create a client, consulting or advisory relationship of any kind.
Architecture decisions, security controls, vendor choices and anything touching money or personal data depend on context we do not have. Treat what you read here as informed input to your own judgement — and to a qualified professional's, where the stakes call for one — not as a substitute for either.
No warranty
The site is provided “as is” and “as available”. We work hard to be accurate and we correct errors promptly when they are pointed out, but we do not warrant that the content is complete, current, error-free or fit for any particular purpose. This field moves quickly: something correct on its publication date may be out of date by the time you read it, which is exactly why every article shows its date.
Limitation of liability
To the fullest extent the law allows, we are not liable for any loss or damage arising from your use of this site or your reliance on anything published here — including lost profits, lost data, downtime, or the cost of a decision that turned out differently than an article suggested it might.
Nothing in these terms excludes or limits liability that cannot lawfully be excluded or limited, and nothing here removes any mandatory consumer rights you have under the law where you live.
Availability and changes
We may change, move, update, archive or remove any part of this site at any time, and we may change these terms. When the terms change, the “last updated” date at the top of this page changes with them; continuing to use the site after that means you accept the revised version. If a provision of these terms turns out to be unenforceable, the rest of them still stand.
Governing law
These terms are governed by the law of the jurisdiction in which the publisher is established, and disputes will be dealt with by the courts of that jurisdiction. Where you are a consumer, this does not deprive you of the protection of mandatory rules of law in your own country of residence, and it does not prevent you from bringing a claim where the law entitles you to. Write to the desk if you need the publisher's establishment details for a formal purpose.
Contact
Questions about these terms, permission requests for republication, and anything else legal go to editors@techagents.online. The other routes into the desk are on the contact page.