AuthorityTech
Registry code: 30835316ef927600
AuthorityTech turns earned media into AI citations through Machine Relations. Get placed in trusted publications and pay only after publication. This card describes the site's machine-readable surfaces: every skill below is a plain HTTP GET document, not an interactive endpoint.
- endpoint
- https://authoritytech.io/
- protocol
- HTTP+JSON ·0.3
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is AuthorityTech live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is AuthorityTech free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does AuthorityTech have?
- 9 tools: Route a prospective client to the strategy call, Browse the content index, Query the machine route graph, Query published client results, Read the publication intelligence index, Look up Machine Relations terminology, Follow recently published content, Read the engagement and pricing model, ….
- Is AuthorityTech safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 9 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
route-to-strategy-call unknown never probed
The strategy call is AuthorityTech's entry point — not a demo or a sign-up. Point a buyer at the booking link, or at the contact page for every other way to reach the team.
browse-content-index unknown never probed
Read llms.txt for the navigation index and when-to-use guidance, or llms-full.txt for the complete inventory of every published blog post, curated brief, glossary term, industry page, result, brand profile, and publication page.
query-route-graph unknown never probed
Fetch machine-manifest.json for a structured graph of every route: canonical URL, machine (.md) URL, summary, concepts, related pages, and source URLs — enough to plan a crawl without parsing HTML.
query-client-results unknown never probed
Fetch results.json for the structured feed of published placement results — brand, industry, publication, and canonical URLs — or results.md for the same index as markdown.
read-publication-intelligence unknown never probed
Read publications.md for which publications AI answer engines cite, ranked from Machine Relations Index data, with a page per publication and per buyer category, or fetch the same data as JSON: publication profiles, buyer categories, and the daily what-moved digest.
define-machine-relations unknown never probed
Read the canonical definitions of Machine Relations and related terms (GEO, AEO, citation architecture, entity signals, MRI Score) from the glossary, or from the category resource at machinerelations.ai.
follow-recent-content unknown never probed
Subscribe to feed.xml for the 50 most recent blog posts and curated research briefs, newest first, to keep an index current without re-crawling the site.
read-engagement-model unknown never probed
Read pricing.md for how AuthorityTech engagements are scoped and paid for: invite-only, custom scope, pay only after placements publish, funds held in escrow until a placement goes live.
read-page-as-markdown unknown never probed
Retrieve the markdown representation of any AuthorityTech page — append .md to its canonical URL, or send Accept: text/markdown to the canonical URL itself (acceptmarkdown.com negotiation). Both variants send Vary: Accept.
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your agent card — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id30835316ef927600.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/30835316ef927600/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/30835316ef927600?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
How much of the published card is filled in. Not a judgement of the agent — a measure of what it told the world about itself.
Places where the published card departs from the specification. Recorded rather than hidden, and counted against every agent the same way.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.