99 Offers Home Seller Match bronze
sellhouse.99offers.io
“Closed-pilot integration for a free, private potential cash-buyer check. Prepare one request from selected, source-tagged facts, update the same draft with missing answers, and read factual status. Record selling preference separately from motivation and timeline; urgency does not imply cash-sale interest or consent. Listing interest is saved, but no active listing service is connected. Obtain an exact homeowner-confirmed property address without guessing. Every supplied top-level homeowner, property, or intent value requires an equal accepted provenance fact. The agent API cannot grant buyer-check or contact-sharing permission; those decisions occur only through the private first-party 99 Offers review flow. A buyer match is not a home offer or sale guarantee.
https://sellhouse.99offers.io/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 6 Dec 2026.Control of the hostname was checked; nothing about who operates it.
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 10 Sep 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇺🇸 US · DigitalOcean, LLC (AS14061)
- Last checked
- 4d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of sellhouse.99offers.io controls every word below.
Prepare a private homeowner request
Create an idempotent draft from current or authorized historical conversation facts, ask only for material gaps, and return both a private first-party review capability and a factual agent_outcome milestone. Reuse grounded context first. Obtain the exact street address from the homeowner or an authorized address tool and have the homeowner confirm it; never infer it from device location, profile location, or old history. Every supplied top-level value must have an equal accepted context_facts item. Never send a raw transcript, open the review link for the person, or infer permission.
- Prepare one private request using selected facts the homeowner has already shared. For each top-level value, include a context_facts record with the same field and value plus its truthful source, confidence, observation time, and confirmation state.
- If the exact property address is missing or unconfirmed, ask the homeowner to confirm it before matching. Use the returned agent_outcome once as the completion milestone, then follow next_action.
Read homeowner-safe request status
Read homeowner-safe status and its factual agent_outcome milestone, and when necessary reconcile an already-started authorized handoff through a read-only lookup. Distinguish eligible route, delivered handoff, and buyer-route activation; never promise a call time. This never starts a route check or a new submission. Poll only while next_action is wait, honor poll_after_seconds, and stop at resolution_deadline, next_action none, or a manual-review message.
- Check the existing task once. If next_action is not wait, stop. If submission status is unknown, never resubmit or create a replacement task.
Add grounded facts to a prepared request
Continue the same A2A task with selected structured facts before any homeowner match or contact consent or route checking. Every supplied top-level patch value requires a matching accepted context_facts item. Preserve explicit selling preference separately from motivation. Retain the existing taskId and contextId; reuse the A2A messageId only with identical facts. REST PATCH and MCP update_homeowner_request provide equivalent draft continuity with shared API idempotency keys. Updates never grant consent, trigger matching or submission, or return the private review token.
- Add property.beds = 4 to the same task together with a context_facts item whose field is property.beds, value is 4, and source and confidence describe where it came from.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- 99 Offers — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.4.0
- Auth schemes
- bearerAuth
- Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- extendedAgentCard pushNotifications streaming
- Agent card
- https://sellhouse.99offers.io/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.