p0stman is an AI-native product studio operated by Thrive Venture Labs Ltd (Norfolk and London, UK), founded by Paul Gosnell. It builds AI voice agents, AI automation, operations command centres, rapid MVPs and "agentic web readiness" rebuilds for clients at fixed prices from £1,500-£8,000, and it uses its own site as the demonstration: p0stman.com serves a live anonymous MCP server at /api/mcp (five tools, JSON-RPC 2.0, protocol 2024-11-05), an A2A agent card for its assistant "Zero" at /.well-known/agent-card.json with a task endpoint at /api/agent, machine-readable JSON at /api/ai/context, /api/ai/services and /api/ai/portfolio, plus llms.txt, agents.md, context.md and a root mcp.json manifest. No OpenAPI, SDK, OAuth surface or developer sign-up is published - the whole API is free, anonymous and read-mostly, with two write tools that book a discovery call or send an enquiry. Not the Postman API platform.
p0stman is listed with 3 APIs on the APIs.io network. Tagged areas include AI Agents, MCP, A2A, Agentic Web, and Voice AI.
p0stman’s developer surface includes documentation, getting-started guide, support, pricing, engineering blog, authentication, and 25 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
AI & Biometrics regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/p0stman-com/"><img src="https://apis.io/badge/p0stman-com/card.svg" alt="p0stman on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Delegated User Identity+6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
7 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
Live, anonymous, remote Model Context Protocol server at https://p0stman.com/api/mcp (JSON-RPC 2.0 over HTTPS POST, protocol 2024-11-05, tools primitive only). Five tools: get_s...
p0stman's agent-to-agent surface: an A2A agent card for "Zero" served at /.well-known/agent-card.json (and the legacy /.well-known/agent.json) on p0stman.com and www.p0stman.com...
Three anonymous JSON endpoints documented in agents.md for agents that do not speak MCP: GET /api/ai/context (company, services, case_studies, contact, how_to_engage, mcp_endpoi...
p0stman ships a live, anonymous, remote MCP server at https://p0stman.com/api/mcp (JSON-RPC 2.0 over HTTPS POST, no session handshake required). It is advertised in llms.txt, ag...
aid: p0stman-com
name: p0stman
description: 'p0stman is an AI-native product studio operated by Thrive Venture Labs Ltd (Norfolk and London, UK), founded
by Paul Gosnell. It builds AI voice agents, AI automation, operations command centres, rapid MVPs and "agentic web readiness"
rebuilds for clients at fixed prices from £1,500-£8,000, and it uses its own site as the demonstration: p0stman.com serves
a live anonymous MCP server at /api/mcp (five tools, JSON-RPC 2.0, protocol 2024-11-05), an A2A agent card for its assistant
"Zero" at /.well-known/agent-card.json with a task endpoint at /api/agent, machine-readable JSON at /api/ai/context, /api/ai/services
and /api/ai/portfolio, plus llms.txt, agents.md, context.md and a root mcp.json manifest. No OpenAPI, SDK, OAuth surface
or developer sign-up is published - the whole API is free, anonymous and read-mostly, with two write tools that book a discovery
call or send an enquiry. Not the Postman API platform.'
deliveryModel:
model: saas
license_evidence:
not_product:
- paulgosnell/zero-agent
open_source: unknown
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: low
source:
- pricing
- repository-not-product
generated: '2026-09-25'
method: derived
image: https://p0stman.com/icon-512.png
url: https://raw.githubusercontent.com/api-evangelist/p0stman-com/refs/heads/main/apis.yml
x-type: company
x-source: harvest:a2a-registry
x-tier: profiled
x-tier-reason: 'enrichment pass 2026-09-19: full contract discovery run; live remote MCP server (5 tools with inputSchema),
A2A agent card at both canonical and legacy paths plus a JSON-RPC task endpoint, llms.txt, agents.md and JSON context endpoints
found on p0stman.com; no OpenAPI, SDK or OAuth surface exists'
specificationVersion: '0.20'
created: '2026-09-19'
modified: '2026-09-19'
tags:
- AI Agents
- MCP
- A2A
- Agentic Web
- Voice AI
- AI Automation
- Product Studio
- Software Development
- Consulting
- United Kingdom
apis:
- aid: p0stman-com:p0stman-mcp-server
name: p0stman MCP Server
description: 'Live, anonymous, remote Model Context Protocol server at https://p0stman.com/api/mcp (JSON-RPC 2.0 over HTTPS
POST, protocol 2024-11-05, tools primitive only). Five tools: get_services (services with GBP "from" prices and timelines),
get_portfolio (case studies, filterable by industry), search_content (guides and pages), and two writes - book_discovery_call
and submit_inquiry - that send a real enquiry to the founder. No authentication, no rate limit published, no idempotency
or reversal path on the writes. Documented in agents.md with a JSON-RPC example per tool; advertised in llms.txt, context.md
and /mcp.json; robots.txt explicitly allows the path.'
image: https://p0stman.com/icon-512.png
humanURL: https://p0stman.com/agents.md
baseURL: https://p0stman.com/api/mcp
tags:
- MCP
- AI Agents
- JSON-RPC
- Services
- Portfolio
properties:
- type: Documentation
url: https://p0stman.com/agents.md
- type: MCPServer
url: mcp/p0stman-com-mcp.yml
- type: Authentication
url: authentication/p0stman-com-authentication.yml
- type: Conventions
url: conventions/p0stman-com-conventions.yml
- type: ErrorCatalog
url: errors/p0stman-com-problem-types.yml
- type: RateLimits
url: rate-limits/p0stman-com-rate-limits.yml
- type: Conformance
url: conformance/p0stman-com-conformance.yml
- type: Lifecycle
url: lifecycle/p0stman-com-lifecycle.yml
overlays: []
- aid: p0stman-com:zero-a2a-agent
name: Zero A2A Agent
description: 'p0stman''s agent-to-agent surface: an A2A agent card for "Zero" served at /.well-known/agent-card.json (and
the legacy /.well-known/agent.json) on p0stman.com and www.p0stman.com, pointing at an anonymous JSON-RPC 2.0 task endpoint
at https://p0stman.com/api/agent. Three skills - inquire (services, pricing, capabilities), portfolio (case studies by
industry) and book (schedule a 30-minute discovery call with Paul Gosnell) - text/plain in and out, no streaming, push
notifications or task history. The card is flavored against A2A 1.0.0 (no protocolVersion, pre-0.3 authentication.schemes).'
image: https://p0stman.com/icon-512.png
humanURL: https://p0stman.com/what-is-a2a-protocol
baseURL: https://p0stman.com/api/agent
tags:
- A2A
- AI Agents
- JSON-RPC
- Booking
properties:
- type: Documentation
url: https://p0stman.com/agents.md
- type: AgentCard
url: a2a/p0stman-com-a2a.yml
- type: Authentication
url: authentication/p0stman-com-authentication.yml
- type: Conventions
url: conventions/p0stman-com-conventions.yml
- type: ErrorCatalog
url: errors/p0stman-com-problem-types.yml
- type: Conformance
url: conformance/p0stman-com-conformance.yml
overlays: []
- aid: p0stman-com:p0stman-ai-context-api
name: p0stman AI Context API
description: 'Three anonymous JSON endpoints documented in agents.md for agents that do not speak MCP: GET /api/ai/context
(company, services, case_studies, contact, how_to_engage, mcp_endpoint), GET /api/ai/services (services with slug, price_from,
currency, timeline, url and subOffers) and GET /api/ai/portfolio (case studies with slug, title, industry, summary, tech,
timeline, url). Read-only, CORS-open, no OpenAPI published - the response shapes are described in prose only.'
image: https://p0stman.com/icon-512.png
humanURL: https://p0stman.com/agents.md
baseURL: https://p0stman.com/api/ai
tags:
- JSON
- AI Agents
- Services
- Portfolio
properties:
- type: Documentation
url: https://p0stman.com/agents.md
- type: Authentication
url: authentication/p0stman-com-authentication.yml
- type: Conventions
url: conventions/p0stman-com-conventions.yml
overlays: []
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: Website
url: https://p0stman.com/
- type: Documentation
url: https://p0stman.com/agents.md
- type: GettingStarted
url: https://p0stman.com/agents.md
- type: Support
url: https://p0stman.com/contact
- type: Contact
url: https://p0stman.com/contact
- type: Pricing
url: https://p0stman.com/pricing
- type: Blog
url: https://p0stman.com/guides
- type: Leadership
url: https://p0stman.com/paulgosnell
- type: TermsOfService
url: https://p0stman.com/terms
- type: PrivacyPolicy
url: https://p0stman.com/privacy
- type: Sitemap
url: https://p0stman.com/sitemap.xml
- type: SourceCode
url: https://github.com/paulgosnell/zero-agent
- type: LinkedIn
url: https://linkedin.com/in/pgosnell
- type: Twitter
url: https://x.com/paulgosnell
- type: LLMsTxt
url: llms/p0stman-com-llms.txt
- type: AgentsMd
url: llms/p0stman-com-agents.md
- type: WellKnown
url: well-known/p0stman-com-well-known.yml
- type: AgentCard
url: a2a/p0stman-com-a2a.yml
- type: MCPServer
url: mcp/p0stman-com-mcp.yml
- type: Authentication
url: authentication/p0stman-com-authentication.yml
- type: Conventions
url: conventions/p0stman-com-conventions.yml
- type: ErrorCatalog
url: errors/p0stman-com-problem-types.yml
- type: RateLimits
url: rate-limits/p0stman-com-rate-limits.yml
- type: Plans
url: plans/p0stman-com-plans-pricing.yml
- type: Conformance
url: conformance/p0stman-com-conformance.yml
- type: Lifecycle
url: lifecycle/p0stman-com-lifecycle.yml
- type: Packages
url: packages/p0stman-com-packages.yml
- type: AgentSkill
url: skills/_index.yml
- type: DomainSecurity
url: security/p0stman-com-domain-security.yml
- type: RegulatoryPosture
url: regulatory/p0stman-com-regulatory-posture.yml
- type: DataSubjectRequest
url: https://p0stman.com/privacy
x-enrichment:
date: '2026-09-19'
status: enriched
artifacts_added: 21
pass: local-v3
p0stman API — frequently asked questions
Does p0stman have an API?
Yes. APIs.io lists 3 APIs from p0stman, including p0stman MCP Server, Zero A2A Agent and p0stman AI Context API.
How do I authenticate with the p0stman API?
p0stman uses bearer-token authentication (1 scheme). The details are profiled on APIs.io as P0Stman Com Authentication.
Does p0stman have an MCP server?
Yes. APIs.io lists 1 MCP server for p0stman: p0stman ships a live, anonymous, remote MCP server at https://p0stman.com/api/mcp (JSON-RPC 2.0 over HTTPS POST, no session handshake required). It is advertised in llms.txt, agents.md, context.md and
Is the p0stman API ready for AI agents?
p0stman has a Kin Score of 27.4 out of 100 (thin) and an Agent Readiness score of 15.2 (agent-aware), scored by API Evangelist on 2026-11-01.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: