Pypestream · Trust Center
Pypestream Trust Center
Trust center
Pypestream maintains a public trust center documenting read_from_source, claims, and note compliance.
CompanyConversational AIAgentic AIContact CenterCustomer ServiceCustomer EngagementChatbotsVoice AIMessagingAnalyticsEnterprise Software
Certifications & Compliance
read_from_sourceclaimsnote
Source
Trust Center
generated: '2026-08-26'
method: searched
source: >-
https://trust.pypestream.com/ (HTTP 200, probed 2026-08-26), https://www.pypestream.ai/security,
and the SSR meta of https://www.pypestream.ai/
trust_center:
url: https://trust.pypestream.com/
http_status: 200
vendor: Vanta
vendor_evidence: >-
Page title "Pypestream Trust Center"; the document loads only assets.vanta.com bundles
(index-trust-report-*.js, alpaca-*.js) and links a Vanta-hosted document at
app.vanta.com/doc?s=mfierwpbr76esz2ac3kgcg.
machine_readable: false
machine_readable_note: >-
The trust center is a client-rendered Vanta application. The HTML delivered to a non-JS client
is a 5.8KB shell containing the page title and nothing else -- no certification list, no
document index, no framework names. https://api.vanta.com/v1/trust-pages/pypestream returns 401.
The certifications Pypestream holds are therefore unreadable by any agent that does not execute
JavaScript, which is the finding: the trust center exists and is not machine-readable.
certifications:
read_from_source: false
claims:
- name: SOC 2
status: claimed
evidence: >-
"SOC 2 certified." appears in the meta name="description", og:description and
twitter:description of every document served by www.pypestream.ai. This is Pypestream's own
first-party assertion in its own markup.
source: https://www.pypestream.ai/
verified_against_report: false
note: >-
Only SOC 2 could be read first-party. The /security page is documented in Pypestream's own
sitemap.xml but the site is a single-page application that returns the identical 375,818-byte
homepage document, canonical https://www.pypestream.ai/, for every route -- so its content was
not machine-readable and no further certification is asserted here. Any additional framework
Pypestream holds is real but unrecorded, not absent; a JS-capable read of
https://trust.pypestream.com/ would resolve it.
security_page:
url: https://www.pypestream.ai/security
http_status: 200
readable: false
note: SPA route; serves the homepage shell to a non-JS client.
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/pypestream-trust-center"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
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.
A second provider on the same verified email joins the account you already have.