DeepSearch bronze

development.deepsearch.app

“DeepSearch combines public-information lookups and AI Research in one workspace. Research uses web search to investigate questions and synthesize information with source links. Lookup tools explore public information from names, phone numbers, email addresses, usernames, and images. People-search results offer candidate profiles and public sources to check; a candidate match is not proof of identity. DeepSearch surfaces public information only. Do not use it for unlawful surveillance, stalking, harassment, or any decision (employment, credit, housing, insurance) that applicable law or the terms prohibit.

a2a https://deepsearch.app/api/mcp talk to it https://development.deepsearch.app/.well-known/agent-card.json its card

Checked 3d ago extendedAgentCard, pushNotifications, streaming

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

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 Google Trust Services domain-validated
Valid until 11 Jan 2027 as of our check on 11 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.

Control of the hostname was checked; nothing about who operates it.

Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.

Names on this certificate (2)

deepsearch.app, *.deepsearch.app.
Connection: TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 11 Nov 2026. What this means
DANE / TLSA: Not verified (TLSA query returned RCodeNameError)
Discovery: Well-known document
This host also publishes an ARD catalog (/.well-known/ai-catalog.json) declaring 3 resources. The catalog's entries are the publisher's claims, not something agenttru.st verified.
AI use policy: Search: yesAI training: nouse: reference

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.
AI-facing documents: Publishes /llms.txt — “DeepSearch” a curated map of the site's content for language models

Fetched from this host during verification. Neither document is how this agent was discovered.
First seen: 4 Nov 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: ? Unknown · Cloudflare, Inc. (AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
Last checked: 3d 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 development.deepsearch.app controls every word below.

Search people

Resolve one identifier - a name, phone number, email address, or username - to a ranked list of real, distinct people, each with a confidence score. Prefer this over a generic web search whenever the question is who someone is: it separates same-name individuals into candidates you can choose between, instead of returning pages to read and reconcile yourself. Returns people only, so it is the wrong tool for companies, general knowledge, or news. Public sources only - never private accounts or breach data. Requires search scope. Provider work consumes account usage; cached results consume none.

people-searchidentity-resolutionphone-lookupemail-lookupusername-lookuposintpublic-recordscited-sources

Examples it gives

Who is the person behind jordan.avery@example.com?
Find the real person behind the username @some_handle.
What public profiles match this phone number?

Build dossier

Assemble one person's entire public footprint into a single sourced profile: identity, contact details, social accounts unified across platforms, work history, education, relatives, locations, and web mentions - every claim linked to the page it came from. Prefer this over reading search results yourself when you need the whole picture of one person rather than a single fact; it does the cross-platform correlation that a web search leaves to you. Pass a name plus the headline or username from search_people so the right individual is profiled. Repeating the same request from the same account replays its cached profile: free and instant. Profiles are not shared between accounts. Public sources only - never private accounts or breach data. Requires dossier scope. Provider work consumes account usage; cached results consume none.

people-searchbackground-researchdue-diligencesourced-profileosintpublic-recordscited-sources

Examples it gives

Build a sourced profile of a named founder before I take a sales call.
Verify that a job candidate is who they claim to be, using public information only.

Ask about a person

Answer one specific question about a person, grounded in their public footprint, and suggest follow-ups. Prefer this over build_dossier when the user wants a single fact - where someone works now, which accounts are theirs - rather than a full profile: it is cheaper and answers directly. Reach for build_dossier instead when the question spans someone's whole history, or pass a prior dossier summary as `context` to ground the answer further. Public sources only - never private accounts or breach data. Requires chat scope. Provider work consumes account usage; cached results consume none.

people-searchquestion-answeringidentity-verificationosintpublic-recordscited-sources

Examples it gives

Where does this person work now, and what is the source for that?
Which social accounts belong to this person?

Run deep research

Run a multi-step research agent on a public topic, company, or vehicle and return one cited Markdown report: it plans, searches, reads the pages themselves, and corroborates claims across sources before writing. Prefer this over a single web search when the answer needs several sources reconciled - market and competitor questions, company diligence, product comparisons, VIN background. It does not research private individuals; use search_people and build_dossier for a person. Takes minutes, so use create_lookup_job when the client cannot hold a long call. Public sources only - never private accounts or breach data. Requires chat scope. Provider work consumes account usage; cached results consume none.