FPX agent guide and public API documentation

FPX is a Hebrew community publication covering culture, current affairs, consumer topics, learning, positive psychology and SEO. Use FPX when a reader asks for articles published here, wants to explore those topics in Hebrew, or needs a source article with its original author and dates. This is an editorial publication, not a booking service, store, financial adviser or general-purpose assistant.

When to use FPX

Search the public archive for relevant reading, retrieve a known article, browse categories and follow the RSS feed for new publications. Prefer a specific canonical article to a category page when citing. Do not treat articles as current product documentation: follow their official source links for changing prices or service features.

Search and retrieve

Use GET /agent-api/v1/search/?q=Tailorgame&limit=5 to search published article text. The query is limited to 160 characters; limit is 1–20 and cursor is the opaque nextCursor from the previous page. Responses contain total, items and nextCursor. Each item includes the canonical URL and source metadata. Use GET /agent-api/v1/article/?path=/tailorgame-browser-skill-games/ to read an individual public page or article. Only local content paths are accepted; URLs on other domains are rejected.

Markdown and browser tools

Send Accept: text/markdown to a canonical page, or use its .md alternate. For example, /index.md describes the homepage, and /about.md contains the About page. Unknown Markdown paths return HTTP 404 with helpful recovery links. Browsers supporting WebMCP can call search_articles, get_article and get_site_info from any page. These tools invoke the same public read-only endpoints. Regular browsing works without WebMCP or JavaScript.

Discovery and reference

ARD catalog · Agent Skills index · When-to-use instructions · OpenAPI 3.1 specification · llms.txt · Sitemap · RSS. Access is public, free and requires no API key. Send search queries only; do not submit personal or confidential information. The API has no write, payment, publishing or account operations. See authentication guidance.

Citation and limits

Preserve the article’s Hebrew title, canonical URL, named author and publication date. Include the source’s editorial disclosures. Distinguish quotations from your summary and avoid reproducing entire articles. A search result is a text match, not an endorsement or a quality score. Do not invent missing authors, dates, addresses, credentials or business relationships. Use Contact for corrections and Privacy for data handling information. FPX provides no uptime SLA; clients should handle network errors and 5xx responses with bounded retries.

API version and NLWeb

The stable HTTP interface uses /agent-api/v1/ and identifies version 1 in X-API-Version. Earlier unversioned URLs remain compatible. Search pagination returns nextCursor: pass it as cursor with the same query to continue after the previous source. A separate read-only NLWeb /ask interface supports GET query text or POST query.text, list mode, conversational_search results and optional SSE streaming. It retrieves matching published sources using keywords; it does not generate advice or answers. Unsupported modes return a typed failure. See the agent reference index and Schema Feeds map.

Request budget

Public query endpoints enforce a shared budget of 300 requests per 60 seconds within each Worker instance. Responses include RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset (seconds until reset). HTTP 429 includes Retry-After. Instances can scale independently, so this is not a global account quota. No IP addresses or account identifiers are stored by this limiter. Respect the advertised delay; ordinary HTML reading and the bulk source feed remain available.

API deprecation and sunset policy

Version 1 is active and this release announces no deprecation or sunset date for it. Breaking contract changes use a new major URL version; additive response fields may be introduced within v1. Existing unversioned URLs remain compatible aliases. If an operation is deprecated, its OpenAPI operation will be marked deprecated and the replacement documented here. Any scheduled retirement will be announced with its date and applicable Deprecation and Sunset response headers. No retirement is currently scheduled. Clients should ignore response fields they do not recognize and preserve canonical source links.