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 JSON to https://forms.avodas.tech/enquiry, use the inquiry form on this site, or email hello@avodas.tech. A person at Avodas reads every request.
The shared service accepts name, email, message and optionally phone, product, city and state. 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 Monday to Friday, 8am to 5pm 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 recognized
An assistant can submit a request, but its identity is separate from the owner who wants the work. Provide the owner name and contact.
Give the owner’s real contact details. We reply to them, not a bot address.
A signature proves which platform you are, not who you act for. We confirm the person separately, by replying to the address you gave.
GET https://forms.avodas.tech/ lists the shared inquiry fields and limits.
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
Use the inquiry form on this site, or POST JSON to https://forms.avodas.tech/enquiry. Include the name and contact of the person who actually wants the work. A person replies.
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 Monday to Friday, 8am to 5pm 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.
Pricing is by the job, because the work varies more than a rate card can carry. A person quotes after reading the request. 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 summarize. The sitemap at /sitemap.xml lists every page.
Not on this site, but requests can be sent programmatically: POST JSON to https://forms.avodas.tech/enquiry (GET https://forms.avodas.tech/ lists the fields), or call submit_request on the MCP server at https://mcp.avodas.tech/mcp. A person reads every one.
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.