# PowerSense public API

Base URL: https://powersense.ro/
OpenAPI: https://powersense.ro/api/openapi.json

The anonymous interfaces and the registered-agent interfaces return only public company and published catalog information. Browser WebMCP continues to use the anonymous interfaces.

## Anonymous company and comparison APIs

GET /ai-brand-profile.json returns the public Organization profile. GET /llms.txt and /llms-full.txt return public reference material. No authentication is required.

GET /wp-json/powersense/v1/systems-comparison?ids=ID1,ID2 accepts one to three actual published system IDs, each a positive integer up to 9999999999. Obtain IDs from the public catalog. The response contains records, unavailable (ID strings), and checked_at. Records include id, url, name, values and public configuration information. Only visible, published, password-free systems are returned; missing or withdrawn systems appear in unavailable. Invalid input returns HTTP 400. Prices are starting prices with their published scope; recheck them before use.

## Live public WooCommerce catalog

GET /wp-json/powersense/v1/catalog reads current published products and exact purchasable variants directly from WooCommerce. Optional query fields: q (up to 100 characters), category (sisteme-fotovoltaice, panouri-fotovoltaice, invertoare, baterii, statii-de-incarcare), limit (1-20, default 10), cursor (the next_cursor returned by the previous page). The response includes products, count, pagination.limit/next_cursor/has_more, checked_at and quotation_services. Follow has_more even when a filtered page contains no products. GET /wp-json/powersense/v1/catalog/{id} rechecks one returned parent product; unavailable or non-public IDs return 404.

Money amounts are integer ISO currency minor units, with metadata.currency_minor_unit identifying their scale. Preserve metadata.tax_display and the exact variant options. price_range describes the included variants, not a binding project quotation. Systems in the photovoltaic category are offered with installation only. metadata.starting_configuration, when present, identifies the public starting configuration. Its installation, mounting and battery scope must remain attached to the price.

Catalog data is not stored as a static feed: each request reads WooCommerce with storefront publication, price and availability filters. Responses are no-store. Recheck before presenting a price or availability. An agent retaining an old response must fetch again. Complete-system availability is commercial availability, not a count of physical complete systems or a promise of installation dates. No internal costs, stock reservations, private inventory counts or customer data are returned.

Custom BESS, C&I and industrial projects remain on the quotation_services URLs. Products without a verified positive public price, hidden or preview products, standalone service add-ons and incomplete variants are excluded. Rate-limited requests receive 429 with Retry-After; invalid input receives 400. Requests must be anonymous and must not carry cookies, WordPress nonces or credentials.

## UCP Catalog

Discovery: /.well-known/ucp. The REST base endpoint is /wp-json/powersense/v1/ucp, with POST /catalog/search, /catalog/lookup and /catalog/product. These read the same live catalog. The supported release is 2026-08-25. Use UCP-Agent containing a public HTTPS platform profile at /.well-known/ucp and a UUID Request-Id. Platform profiles are fetched and negotiated with bounded public-network requests; a valid profile must offer the requested catalog capability. No UCP checkout, cart, orders, payment handlers, sign-in or payment operations are provided. See the OpenAPI operations for supported fields and request limits.

## Anonymous MCP

POST /wp-json/powersense/v1/mcp is a stateless Streamable HTTP endpoint without authentication. Do not send cookies or credentials. Send Content-Type: application/json and Accept: application/json, text/event-stream. Initialize first, then send notifications/initialized, tools/list and tools/call. Send the negotiated MCP-Protocol-Version header on subsequent requests. Tools: company_profile with empty arguments; compare_systems with an ids array of one to three unique positive integers; catalog_search with optional q, category, limit and cursor; catalog_product with a parent product id. There are no private operations, sessions or server-pushed streams. GET and DELETE return 405. An accepted notification receives 202 with an empty body.

## Registered-agent access

Register a confidential machine client through https://powersense.ro/wp-json/powersense/v1/agent-auth/register, then obtain a client_credentials token through https://powersense.ro/wp-json/powersense/v1/agent-auth/token. Issuer: https://powersense.ro/agent-auth. Read https://powersense.ro/auth.md for exact registration, token, revocation and unregister requests.

The only scope is powersense.public.read. resource is mandatory when requesting a token. Use https://powersense.ro for POST /wp-json/powersense/v1/agent/company (JSON {}) or POST /wp-json/powersense/v1/agent/compare (JSON {"ids":[ID1,ID2]}). Use https://powersense.ro/wp-json/powersense/v1/agent-mcp for POST /wp-json/powersense/v1/agent-mcp, with the same MCP protocol and public read-only tools described above. These audiences are separate; tokens are not interchangeable.

Supply Authorization: Bearer <access_token> on every protected request. Missing, expired or revoked tokens receive 401; insufficient scope is rejected. Registered-agent MCP includes its path-specific resource_metadata URL in the Bearer challenge. Credentials grant no WordPress login or ERP access. Registration and revocation manage agent credentials only.

OAuth metadata: /.well-known/oauth-protected-resource for the logical public-data API; /.well-known/oauth-protected-resource/wp-json/powersense/v1/agent-mcp for registered-agent MCP; /.well-known/oauth-authorization-server/agent-auth for the dedicated issuer. The site-root OAuth issuer and legacy MCP remain separate.

## Browser tools

Supporting browsers register powersense_company_profile and powersense_compare_systems through WebMCP. Standard browsers keep the ordinary site experience. Browser calls use the anonymous JSON APIs and never store client secrets or bearer tokens.

## Discovery and representations

GET/HEAD /.well-known/api-catalog returns application/linkset+json. ARD: /.well-known/ard.json; compatibility catalog: /.well-known/ai-catalog.json. Skills: /.well-known/agent-skills/index.json. MCP server card: /.well-known/mcp/server-card.json. GET /api/agent-status.json reports only that discovery document serving is running; it does not check ERP, product availability or external services.

GET/HEAD /.well-known/poppy.json declares website-only discovery under Personal Agent Protocol draft 0.1. Its empty web object supports ordinary public browsing only. It does not advertise Poppy sessions, sign-in, conversations or Poppy-authorized APIs; the API and MCP access described above remain separate.

For eligible anonymous public pages, send Accept: text/markdown. HTML remains the browser default. Responses vary by Accept. Markdown responses are not stored in shared caches. The optional x-markdown-tokens value is an estimate.

Content use: search=yes, ai-input=yes, ai-train=yes. Access instructions: /auth.md.
