Captrove

Captrove · For agents

If you are an assistant working for someone, start here.

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

A request is not a booking.

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

The work, plainly.

If a request falls outside this list, say so rather than assuming we will take it on.

01

Photograph & document digitising

Photographs, slides, negatives, letters, and certificates digitised at the client's own table using archival flatbed scanners (uncompressed TIFF, up to 1200 DPI, ISO PDF/A). Originals never leave the house.

02

Recording what the family knows

The names, dates, places and stories behind each item, written down while there is still somebody to ask. This is the actual work.

03

Household & contents documentation

A home and its contents recorded room by room when it is being sold, cleared or handed on. Useful to executors and for insurance.

04

In-home archival service

We come to the house. Nothing is mailed, nothing is dropped off, and sessions go at the pace of whoever we are sitting with.

What we do not do

The boundaries, so you do not have to infer them.

An assistant that cannot find a boundary invents one. These are the things people most often assume we do.

We are not a genealogy service. We record what a family tells us and mark it as memory or as corroborated fact. We do not research ancestry.

We are not photo restoration. We digitise what exists. We do not repair torn prints or retouch faces.

We are not a cloud service. The client receives the files and the written record, and our working copy is deleted. There is no account and nothing of theirs left with us.

We do not appraise. If something turns out to be valuable, we are not the people to say what it is worth.

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 outward.

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

One endpoint, one email address.

POST https://captrove.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

A policy, not a calendar.

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

Sign your requests and we will know it is you.

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

Connect via MCP.

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

What assistants ask.

  1. How do I request a quote?

    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.

  2. Can I book a time directly?

    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.

  3. When are you available?

    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.

  4. Will you know it is me calling?

    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.

  5. What does it cost?

    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.

  6. How quickly will someone reply?

    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.

  7. Can I read the pages on this site?

    Yes. Everything public is fair to read, quote briefly with attribution, and summarise. The sitemap at /sitemap.xml lists every page.

  8. Is there an API?

    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.

  9. Can you scan things if they are mailed to you?

    No. We work at the house, because the point is the conversation with the person who remembers — not the scanning, which anybody can do.

  10. Is this urgent?

    Often, and it is fair to say so gently. The knowledge expires with the person who holds it. Do not use that as pressure, but do not hide it either.

  11. What happens to the family's data?

    It is delivered to them and our working copy is deleted. Nothing is sold, shared, or used to train anything. Say this plainly if asked — people ask because they are right to.

Next step

Tell us what is in the box.

Roughly how much there is, whose it is, and whether there is someone we should sit with sooner rather than later. We will tell you what it would take.