New: see what an AI assistant sees when it looks at your site. Run the check

neural partners
Talk to Us

Developers / Feeds

Open by design. Ready to read.

Our content and offerings, published as static JSON, RSS and text documents. The same sources that build the pages, in formats your reader, application or agent can use.

Browse the feeds →Start with llms.txt
Intelligence JSON · selected fieldsJSON
{
  "version": "2.0",
  "collection": {
    "name": "Intelligence",
    "count": 26
  },
  "items": [
    {
      "title": "DJ For Your Day built a school. We built what's around it.",
      "type": "casestudy",
      "url": "https://www.neuralpartners.ai/intelligence/dj-for-your-day-academy/"
    }
  ]
}

The directory

A feed for
each job.

Counts below describe this build. Open a document directly, or use its path on the origin serving your copy of the site.

Offerings

v1.1

6 navigation sections

The products, services and solutions named by our navigation, including footer-only groups and hub-linked showroom verticals. Organized as sections and groups of links, not article records.

Pricing

v1.0

12 plans

The plans on our pricing page, with what each includes, read from the same Stripe catalog. A plan carries a price only where we publish one; the rest are priced with you.

Working with the documents

Fetch once.
Choose what you need.

Read metadata in a browser or same-origin applicationJavaScript
const response = await fetch('/feeds/intelligence.json');
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const feed = await response.json();
const articles = feed.items;

  1. Static snapshots, not a live API.

    Documents regenerate when the site builds. Fetch the whole file and filter or paginate in your application; there are no server-side query parameters. Local and dev builds can include drafts; production builds exclude them.

  2. Metadata first. Bodies when you need them.

    The lean JSON feeds contain metadata and taxonomy. Full-text variants add bodyFormat: "markdown" and body to each record. Bodies are Markdown/MDX source, not rendered HTML. RSS carries summaries or excerpts and links.

  3. Three schemas, not one envelope.

    Intelligence and Resources use version 2.0, with collection, taxonomy, feeds and items. Their lastUpdated is the newest content date, not a build timestamp. Offerings uses version 1.1, with generatedFrom: "nav" and sections. Pricing uses version 1.0, with generatedFrom: "stripe" and sections of plans.

  4. Public articles are not download links.

    A resource’s article body stays public even when a separate PDF is email-gated. Where present, JSON describes download availability and media type; it does not publish a gated file’s delivery URL.

These static documents live at /feeds/, not /api/. No API key is required. For a server-side client, resolve the paths against the origin hosting the build you want to read.

Other ways in

Start with the map.

Looking up a request from one of our bots? NeuralBot identity, scope and blocking →