# TechSee

> TechSee builds visual assistance and visual agentic AI for customer service, contact
> centers and field service. Its platform — TechSee Live for agent-guided visual
> sessions and Sophie AI for autonomous multimodal virtual agents — combines live
> video, computer vision, augmented reality overlays and screen sharing so a human or
> AI agent can see what a customer sees and guide them to a resolution. TechSee sells
> into telecommunications, insurance, utilities, consumer electronics, home builders,
> medical devices, retail and BPO.

Generated by API Evangelist on 2026-08-29 from this repository and from live probes of
TechSee's public surface. TechSee does not publish an llms.txt of its own
(https://techsee.com/llms.txt returns 404), so this file is generated, not harvested.

## What is callable today

- [MCP server](https://techsee.com/wp-json/mcp/mcp-oauth-server): live, OAuth-protected
  Model Context Protocol endpoint on techsee.com. Verified by probe: an unauthenticated
  GET returns HTTP 401 `{"code":"mcp_unauthorized"}`. IMPORTANT: this is the WordPress
  MCP surface of the techsee.com marketing site (the /wp-json/mcp/ adapter alongside
  /wp-json/wp-abilities/v1/), not the TechSee Live or Sophie AI product API. Its tools
  are WordPress site abilities. Do not assume visual-assistance sessions are callable
  over MCP; they are not, publicly.
- [OAuth authorization server metadata](https://techsee.com/.well-known/oauth-authorization-server):
  RFC 8414. Authorization code + refresh token, PKCE S256 required, public clients only
  (`token_endpoint_auth_methods_supported: ["none"]`), client-ID metadata documents,
  single scope `mcp`.
- [OAuth protected resource metadata](https://techsee.com/.well-known/oauth-protected-resource):
  RFC 9728, naming the MCP endpoint as the protected resource.
- [TechSee Live iOS SDK](https://github.com/TechSeeDev/TechSee-Live-Framework): Swift
  Package, latest tag 5.4.5 (2024-09-24). Embeds a TechSee visual assistance session in
  a host iOS app — screen and application mirroring, video and photo modes, image
  upload, text chat, pause/resume, 24 UI languages, iOS 13+. Binary targets are pinned
  xcframework archives on TechSee's own CDN at sdk-us.techsee.me.

## What is NOT available

- No OpenAPI, Swagger, AsyncAPI, GraphQL SDL, Protobuf or WSDL contract is published
  anywhere. Probed: api.techsee.me (/openapi.json, /openapi.yaml, /swagger.json,
  /v1/openapi.json, /api-docs, /docs, /redoc, /swagger — all 404), techsee.com and
  app.techsee.me.
- No public API reference. TechSee markets an "open integration platform" of APIs, but
  the former developer portal at https://techsee.readme.io/ answers HTTP 401 and the
  Stoplight workspace at https://techsee.stoplight.io/ answers 200 with zero public
  projects (the workspace has been locked since 2023-07-31).
- No A2A agent card. /.well-known/agent-card.json and /.well-known/agent.json return
  404 on techsee.com and api.techsee.me; app.techsee.me answers 200 for every
  /.well-known/* path with the same 1,003-byte SPA shell, which is not a card.
- No security.txt, no /.well-known/api-catalog, no OpenID Connect discovery.
- No published pricing. Pricing is contact-sales only.
- No published rate limits, changelog, status page, sandbox, CLI or Postman collection.

## Company

- [Website](https://techsee.com/)
- [About](https://techsee.com/about-us/)
- [Technology](https://techsee.com/technology/)
- [Integrations](https://techsee.com/integrations/): Salesforce, ServiceNow, Zendesk,
  Amazon Connect, Oracle, Pega, Microsoft Dynamics 365, Amdocs, CSG, AWS, ChatGPT
- [Pricing](https://techsee.com/pricing/) (contact sales)
- [Blog](https://techsee.com/blog/)
- [Support](https://techsee.atlassian.net/servicedesk/customer/portal/5) (Atlassian
  service desk, login required)
- [GitHub organization](https://github.com/TechSeeDev)
- [Terms and conditions](https://techsee.com/terms-and-conditions/)
- [Privacy policy](https://techsee.com/privacy-policy/)
- [Application login](https://app.techsee.me/)

## Domain security posture (probed 2026-08-29)

TLS 1.3 with HSTS (max-age 31536000) on techsee.com. The registrable domain publishes
no DNSSEC, no CAA, no SPF and no DMARC record.

## Machine-readable artifacts in this profile

- apis.yml — APIs.json profile with every pointer
- mcp/techsee-mcp.yml — the MCP server manifest
- well-known/techsee-well-known.yml — the /.well-known/ probe record and raw documents
- authentication/techsee-authentication.yml — OAuth 2.0 profile read from live metadata
- scopes/techsee-scopes.yml — the single `mcp` scope
- conformance/techsee-conformance.yml — RFC 6749/6750/7636/8414/9728 + MCP conformance
- packages/techsee-packages.yml — the iOS SDK and the @techsee npm packages
- plans/techsee-plans-pricing.yml — plan_count 0, contact sales
- rate-limits/techsee-rate-limits.yml — limit_count 0, undocumented
- security/techsee-domain-security.yml — TLS/HSTS/DNS probe

This profile is maintained by API Evangelist and is not published by TechSee.