ilovepsxAPI
Skip to documentation
AI INTEGRATION RESOURCES

Build with your AI assistant

Give your assistant the API contract, the data conventions and a useful starting prompt. Keep your key in your server environment.

Three steps to useful code

  1. Copy the prompt below and add your language, dataset and intended application.
  2. Let an assistant with web access fetch the documentation. If it cannot read URLs, download the full context or OpenAPI file and attach it.
  3. Review the generated requests, set ILOVEPSX_API_KEY on your server, and test against your own account. Preserve exact values and missing data.
Public integration prompt
Use the ILovePSX Funds API to implement my integration. First read https://funds.api.ilovepsx.com/llms.txt and https://funds.api.ilovepsx.com/docs/index.md, then the relevant operations in https://funds.api.ilovepsx.com/docs/reference.md or import https://funds.api.ilovepsx.com/docs/openapi. Ask me which language and dataset I need. Use only published endpoints. Read ILOVEPSX_API_KEY from a server environment variable; never ask me to paste a secret into chat. Discover fund slugs from the registry. Preserve exact decimal strings, nulls, source dates, FMR reporting periods and provenance. Handle pagination, missing reports, 304, 429 Retry-After and bounded retries. Do not invent coverage, analytics endpoints, SDKs or an MCP server. Clearly label synthetic examples and cite the documentation used. Produce runnable server-side code and explain setup and error handling.

Choose your context

Start small

A compact index that helps an assistant find the relevant guide and contract.

/llms.txt ↗
Download

Developer guide

Setup, authentication, interpretation, pagination, bounds and error handling.

/docs/index.md ↗
Download

Endpoint reference

Generated parameters, request bodies, costs, three-language examples and shared schemas.

/docs/reference.md ↗
Download

Complete context

The guide and full reference in a single text file for attachment or local retrieval.

/llms-full.txt ↗
Download

OpenAPI JSON

A sanitized contract to import into an API client or code generator. Dataset response typing is partial.

/docs/openapi ↗
Download

Help the assistant get the details right

  • Use only the published fund endpoints; discover slugs through the registry.
  • Keep keys out of prompts, screenshots, browser code and logs.
  • Financial decimals remain strings until handled by decimal arithmetic. Null does not mean zero.
  • Latest NAV, monthly report period and response generation time are separate dates.
  • Follow pagination, respect Retry-After, and make retries bounded.
  • Report coverage varies. Synthetic teaching models are not production observations.
  • The OpenAPI data envelope is partially typed; inspect dataset examples and real explorer responses before generating a strict client model.

llms.txt is a public documentation index following the llms.txt proposal. Tool support varies. These files provide context; they do not install an SDK, expose a hosted MCP server, change crawler permissions or give an assistant account access.

Review the endpoint reference ↗