Developer.sailpoint.com is now AI-readable

Hello Developer Community!

We are very excited to announce a feature recently added to developer.sailpoint.com. AI has completely changed how we work and so our developer docs needed a change too :tetry:

Many of you now use AI assistants like Claude, ChatGPT, Cursor, and Copilot when you build on SailPoint. These tools do their best work when they can read the developer docs as clean text, not as rendered HTML full of navigation and scripts.

Starting today, the SailPoint Developer site publishes its content in formats built for LLMs, and every developer docs page has a button to send it straight to your AI tool.

New: the Copy page button

Every developer docs page now has a Copy page button next to the title. It gives you four options:

  • Copy page: copies the whole page to your clipboard as clean Markdown, ready to paste into any chat or prompt.
  • View as Markdown: opens the raw Markdown version of the page in a new tab.
  • Open in ChatGPT: starts a new ChatGPT conversation with the page already loaded.
  • Open in Claude: starts a new Claude conversation with the page already loaded.

Say you’re reading an API reference page and want help writing a script against that endpoint. Click Open in Claude or Open in ChatGPT and ask your question. The assistant already has the page.

More ways for AI tools to read the developer docs

/llms.txt: a map of the whole site
developer.sailpoint.com/llms.txt is a plain-text index of every developer docs page, grouped by sidebar section, with a link and short description for each. It follows the open llms.txt standard, so AI tools and agents can find the right page without crawling the site.

/llms-full.txt: all the developer docs in one file
developer.sailpoint.com/llms-full.txt combines every developer docs page into one file, in sidebar order. Use it when you want to give a model the full developer docs at once, for example in a RAG index or a long-context session.

Any page as Markdown: add .md to the URL
Every developer docs page also has a raw Markdown version. Add .md to the end of the page path:

https://developer.sailpoint.com/docs/api/authentication
https://developer.sailpoint.com/docs/api/authentication.md

You get clean Markdown with the page title and no frontmatter. This covers our API reference for Identity Security Cloud, IdentityIQ, and Non-Employee Risk Management, plus the guides for connectivity, extensibility, and more.

Automatic discovery
Every page includes a <link rel="alternate" type="text/plain" href="/llms.txt"> tag, so AI crawlers and agents that support the standard can find the index on their own.

Why it matters

  • Better answers. When your assistant reads the real developer docs, it is less likely to make up endpoints, fields, or query parameters.
  • Less copy-and-paste cleanup. Markdown keeps the headings, tables, and code samples that copying from a web page often breaks.
  • Easier integrations. If you build internal chatbots, support tools, or agents that work with SailPoint APIs, you now have a stable, machine-readable source to point them at.

Try it

  1. Open any developer docs page on developer.sailpoint.com and click Copy page next to the title.
  2. Choose Open in Claude or Open in ChatGPT and ask a question about the page.
  3. If you’re building an agent, point it at https://developer.sailpoint.com/llms.txt so it can find the pages it needs.
  4. Tell us what you build with it, and what would make it more useful, here in the Developer Community.
18 Likes

Are there plans to add more IdentityIQ docs to this? Seems like the perfect time to do it since community is offline. I only see 14 docs related to IIQ and it looks like around ~14,500 related to ISC, but my count could be way off.

1 Like

I’m sure the team has already thought of this, but we need the same thing done to the content on the documentation site.

I’ve mentioned this to Tyler, but ServiceNow converts all their documentation to markdown and hosts it in github - this is really helpful when building out agent skills

2 Likes

of course

You’re right

1000% echoing Cheek here. The connector docs are not very AI-friendly, and it takes a lot of tokens for Claude to crawl a single connector’s docs.

Hi everyone!

Thank you so much for your suggestions, and thank you to our Developer Relations team for kicking this off. We’ve added two ways to obtain the SaaS documentation’s source Markdown. Each page can be copied individually, or you can download the entire doc set via the link in the footer.

This functionality is not yet available in the connector documentation, as we are finalizing major updates and improvements that will make that content easier to navigate, search, and provide to LLMs. I can’t wait to share more details with you soon.

1 Like