Developers

Syncek for developers and agents

Everything on this page is public, needs no key and no account, and is served from stable URLs. If you are a program, start with the OpenAPI description; if you are a person deciding whether Syncek fits your stack, start with the section on the product API.

What Syncek publishes today

These are read-only endpoints describing this website: what the product is, what it costs, what the documentation says, and what changed. They exist so a program does not have to parse HTML.

  • https://syncek.com/llms-full.txt

    Syncek extended reference. Full product overview, per-plan pricing and contents, the comparison table, complete FAQ answers and recent releases.

  • https://syncek.com/md

    Syncek site summary as markdown. The same document as this one, served as text/markdown instead of text/plain. Also served from the homepage when the request carries Accept: text/markdown.

  • https://syncek.com/docs/changelog.md

    Syncek documentation as markdown. Append .md to any documentation URL for the same markdown the page renders. This link is the changelog; section indexes and single guides work the same way.

  • https://syncek.com/docs/search-index.json

    Syncek documentation search index. Every guide, section index and changelog entry as one JSON array, with body text for matching. The cheapest way to resolve a topic to a URL.

  • https://syncek.com/data/crm-pricing.json

    SMB CRM pricing dataset by Syncek. Entry pricing for twenty CRMs, each figure read from the vendor's own page on a recorded date, with the source and the change series between readings. CC BY 4.0.

  • https://syncek.com/blog/rss.xml

    Syncek blog feed. RSS 2.0, newest first.

  • https://syncek.com/docs/changelog/rss.xml

    Syncek changelog feed. RSS 2.0 of everything shipped, newest first.

  • https://syncek.com/sitemap-index.xml

    Syncek sitemap index. Every indexable URL, per locale, with last-modified dates.

  • https://syncek.com/.well-known/security.txt

    Syncek security disclosure policy. Where to report a vulnerability, which languages we read, and the policy behind it. RFC 9116.

  • https://syncek.com/robots.txt

    Syncek crawl policy. Content-Signal declaration and the AI crawler allowlist. Read it before fetching at volume.

  • https://syncek.com/openapi.json

    Syncek OpenAPI description. OpenAPI 3.1 description of every endpoint on this list, each with an operation id, a description and a response schema. Also advertised on every page response as a Link header with rel="service-desc".

The Syncek product API

Syncek includes a REST API over the same endpoints the application itself uses, from the Business plan upward. It is not publicly reachable yet: the product is in early access, access is by waitlist, and there is no self-serve signup. When it opens it will be documented at its own origin, with its own OpenAPI description and its own authentication. The document linked above deliberately describes this website and not that API, because a specification whose endpoints do not answer is worse than none.

See what each plan includes

Reading this site as an agent

  • Send `Accept: text/markdown` to any locale home page and you get the site summary as markdown instead of the rendered page: a few kilobytes rather than several hundred.
  • Append `.md` to any documentation URL for the same markdown the page renders, from the same source, so the two cannot disagree.
  • A URL that resolves to nothing answers 404. Ask for markdown and the body is a short recovery note pointing at the sitemap and the surfaces above, rather than an HTML app shell.
  • A composed documentation path that does not exist answers RFC 9457 `application/problem+json`, so a missing guide is distinguishable from an outage.
  • Crawling is welcome. `robots.txt` carries a Content-Signal declaration and names the AI crawlers explicitly; read it before fetching at volume.

Reuse and licence

The CRM pricing dataset is published under CC BY 4.0: quote it, chart it, or check it, and attribute Syncek with a link to the comparison page it renders on. Each figure records the vendor page it was read from, the date it was read, and whether that page needed a browser, because an automated pass over those same pages once produced prices that were footnote markers. Everything else here is ordinary site content.