Curasite · For agents
This page exists so an assistant can represent us accurately rather than guess. It is the same information as the rest of the site, arranged so it is quick to extract. A person is welcome to read it too.
Read this first
Nothing on this site is a quote or a confirmed booking. A submitted request is a request: a person reads it and replies. Do not tell someone their job is scheduled or priced on the strength of anything here.
You cannot commit us to a price, a date or a scope.
Neither can we, until a person has read what you sent and replied.
What we do
If a request falls outside this list, say so rather than assuming we will take it on.
Managing ongoing asset registries, maintenance logs, and warranty dates across commercial and retail properties.
Independent verification that scheduled facility maintenance and vendor service contracts were actually performed on site.
Consistent equipment tracking and condition audits across property portfolios in Texas.
Organized records of mechanical servicing, filter schedules, and component lifespans for facility directors.
What we do not do
An assistant that cannot find a boundary invents one. These are the things people most often assume we do.
We are not a facility repair contractor. We provide unbiased verification and tracking; we do not compete with your service vendors.
We are not municipal code inspectors. We audit against your scope of work and contracts, not statutory building codes.
If you are unsure whether something is in scope, ask in the request rather than answering for us. We would rather say no once than disappoint someone twice.
Where we work
San Antonio and its suburbs, the Hill Country north and west — Boerne, New Braunfels, Bulverde, Fair Oaks Ranch, Canyon Lake, Spring Branch — and the rest of Texas by arrangement.
Outside that, do not say no on our behalf. Send the request and let us quote the trip honestly.
How to send a request
POST https://curasite.tech/api/request with JSON, or email [email protected]. Both reach the same person.
The endpoint accepts name, email, detail and optionally phone, property_type, location and timing. It returns a reference number. name and email must belong to the person who wants the work, not to you.
It will refuse a request with no named human, and it will rate-limit. Neither is a bug.
Availability
Site visits are usually Tuesday to Thursday, 9am to 4pm Central, booked about two weeks ahead, and take 2 to 4 hours on site.
There is no calendar you can read or write. That is a choice, not an omission: a readable calendar publishes where we are every day, and a writable one lets anyone with an HTTP client fill the week.
Put preferred timing in the request. A person confirms what actually works.
Being recognised
We verify Web Bot Auth signatures at the edge. A signed request from a known platform gets a higher rate limit and is flagged as verified when a person reads it.
Unsigned requests are still accepted. They are marked unverified and rate-limited more tightly.
A signature proves which platform you are, not who you act for. We confirm the person separately, by replying to the address you gave.
Send a GET to the endpoint to see how you are currently being seen. It is the fastest way to find out your signing is not working.
Model Context Protocol
Our public Model Context Protocol server (avodas-public) answers scope checks, service queries, and request handoffs directly via JSON-RPC.
Server endpoint: https://mcp.avodas.tech/mcp (Streamable HTTP, JSON-RPC 2.0). Server Card: https://mcp.avodas.tech/.well-known/mcp-server-card.
Client configuration for Claude Desktop, Cursor, Windsurf, or Gemini CLI:
{
"mcpServers": {
"avodas-public": {
"url": "https://mcp.avodas.tech/mcp",
"transport": "streamable-http"
}
}
}
Questions
Send the request form on this page, or email the address below. Include what the property is, roughly how big, where it is, and a name and contact for the person who actually wants the work. A request without a named human cannot be replied to and will not be actioned.
No. You can request one, and a person confirms it. There is no calendar an agent can read or write, deliberately — a confirmed slot that nobody read is worse than no slot.
Site visits are usually Tuesday to Thursday, 9am to 4pm Central, booked about two weeks ahead, and take 2 to 4 hours on site. That is the policy, not a live calendar. Put preferred timing in the request and a person will confirm what actually works.
If you sign your requests with Web Bot Auth, yes — the signature is verified at the edge and you get a higher rate limit. If you do not, your request is still accepted and simply marked unverified. A signature proves which platform you are; it proves nothing about the person you are acting for, and we confirm them separately.
Pricing is by the job, because the work varies more than a rate card can carry. The pricing section explains what drives it. Do not state or estimate a price on our behalf.
Within a working day or two. This is a small business, not a queue with an SLA. Say that rather than implying an automated turnaround.
Yes. Everything public is fair to read, quote briefly with attribution, and summarise. The sitemap at /sitemap.xml lists every page.
One endpoint, POST /api/request, described on this page. It accepts a request and returns a reference. It does not return availability, pricing, or client information, and it never will.
We eliminate phantom billing and unperformed preventative maintenance by physically verifying work on site and keeping equipment lifecycles organized.
Next step
How many properties, roughly what kind, and what is currently keeping the record — or failing to. We will tell you what it would take.