# Build with AI (/data-api/guides/ai-tools)

Connect your coding assistant to Fiskil documentation and build against the current API reference.



Connect your coding assistant to Fiskil's documentation before asking it to write an integration. The documentation MCP server provides search, API schemas and examples without a Fiskil account or API key.

Connect your assistant [#connect-your-assistant]

Use the [MCP setup guide](/data-api/guides/ai-tools/mcp) for **Codex, Claude Code, Cursor, GitHub Copilot or Gemini CLI**. Start with the instructions for your client, then make a tool call to verify the connection.

The server reads public documentation. It cannot access customer accounts, create consents or call the Data API on your behalf. The optional feedback tool sends documentation feedback to Fiskil.

Start an integration [#start-an-integration]

After connecting, paste this prompt and describe your application:

```text
Help me integrate Fiskil into this project. Inspect the existing stack and
ask which data I need and which Fiskil API version the integration uses.

Use the Fiskil documentation MCP server to read the quick start,
authentication, API versioning, Link SDK and webhook guides. Discover
endpoints with list_api_endpoints, then read the API reference for the
chosen version before writing requests or response types. Do not invent
endpoint paths, parameters or fields.

Keep API credentials and token exchange on the backend. Create an end user
and auth session, then launch the Link SDK in the frontend. Handle every
consent ID in the SDK's consents array. Keep end_user_id and consent IDs
separate; use the identifier required by each API endpoint.

Verify webhook signatures against the exact request bytes, handle duplicate
deliveries and wait for the relevant data-ready events. Follow the documented
pagination and rate-limit behaviour. Use the existing project's conventions.

Implement the smallest working integration, test success and failure paths,
and link the Fiskil pages used. Tell me what still needs credentials or a
real institution connection to test.
```

For a smaller task, ask the assistant to read the relevant guide first:

* “Use the Fiskil docs to add Link SDK 1.0.0 and handle multiple consent IDs.”
* “Read the webhook guide and test signature verification with a tampered body.”
* “Read the historical balances guide and explain the limits of calculating a running balance.”

Keep the documentation in context [#keep-the-documentation-in-context]

Add this short instruction to your project's `AGENTS.md` for Codex or `CLAUDE.md` for Claude Code. Merge it into an existing file rather than replacing the file.

```markdown
For Fiskil integration work, use the Fiskil documentation MCP server to
check the relevant guide and API reference before writing code. Confirm
the API version, endpoint path, required identifiers and response shape.
If MCP is unavailable, start at https://docs.fiskil.com/llms.txt and fetch
the relevant pages. State when documentation could not be retrieved.
```

These are project instructions, not a plugin installation. MCP supplies current documentation when the assistant needs it.

Use documentation without MCP [#use-documentation-without-mcp]

If your assistant can fetch URLs, ask it to read the index and only the pages relevant to your task. If it cannot fetch URLs, paste the relevant page content into the conversation.

| Resource                                                                                      | Use                                                                                                                             |
| --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| [llms.txt](https://docs.fiskil.com/llms.txt)                                                  | Find documentation pages and their URLs.                                                                                        |
| [A page as Markdown](https://docs.fiskil.com/data-api/guides/getting-started/quick-start.mdx) | Append `.mdx` to a documentation page URL to retrieve its content.                                                              |
| [skill.md](https://docs.fiskil.com/skill.md)                                                  | Read a brief introduction to Fiskil's capabilities and documentation. This is a reference page, not an installable agent skill. |
| [llms-full.txt](https://docs.fiskil.com/llms-full.txt)                                        | Retrieve the documentation in one file when your tool can handle a large context. Prefer individual pages for focused tasks.    |

Review generated code before using it with real data. Test with your sandbox credentials and keep credentials, tokens and customer data out of prompts and documentation feedback.
