Reuse the public technical catalogue.

Public JSON API

The canonical endpoint is /wp-json/openvist/v1/sites/. Results are paginated and contain only published project records. Use page and per_page (maximum 100), or narrow results with q and a project-category category slug.

What a record contains

Each record can include a stable WordPress identifier, name, domain, official URL, canonical OpenViST URLs, category path, directory summary, practical profile sections and evidence-backed public details. Unknown or private workflow data is not exported.

Project sources and scope

OpenViST focuses on AI, agents, blockchain and crypto. Official project websites, repositories, technical documentation and publisher-identified application records support the public profiles. Discovery lists do not establish technical capabilities or authorize publication.

Boundaries and rights

Private account data, claim evidence, reports, security information and personal correspondence are excluded. Website names, logos and linked third-party material may carry separate rights; API availability does not grant rights in those assets. OpenViST prepares a static daily catalogue snapshot in JSONL.gz and CSV.gz shards, accompanied by a versioned manifest, record counts and SHA-256 checksums. The files contain public records only and are generated in recoverable background batches rather than on each download.

Recipes and browser Tools source

The public recipe library on GitHub contains exported published recipes, organised by language and version. The recipe catalogue API is separate from the project Directory API. Browser Tools source, documentation and tests are available under projects/browser-tools. Check the licence distributed with each file; plugin integration and standalone processing code can have different licences. Tool inputs and results are not part of these public exports.

Journal reuse: CC BY 4.0

From 16 October 2026, the original editorial text of existing and future OpenViST Journal articles is available under Creative Commons Attribution 4.0 International (CC BY 4.0), unless a specific notice states otherwise. You may share, reproduce, translate and adapt that text, including for commercial purposes. This grant applies only to rights OpenViST can license.

How to give credit

• Name OpenViST and retain any separately required author attribution, copyright notices and disclaimers.
• Identify the article and provide its original URL. For online reuse, link to that article; for offline use, provide the URL in the credit.
• Name and link to CC BY 4.0.
• State whether you changed, shortened, translated or otherwise adapted the text, retaining any existing change notices.
• Do not suggest that OpenViST endorses your publication or adaptation. Do not add legal or technological restrictions that prevent exercise of the licensed rights.

Example: unchanged text

“How to Read a Repository Before You Build on It” — OpenViST. Source: https://openvist.com/how-to-read-a-repository-before-you-build-on-it/. Licensed under CC BY 4.0. Changes: none.

Example: translation or adaptation

Adapted from “How to Read a Repository Before You Build on It” by OpenViST. Source: https://openvist.com/how-to-read-a-repository-before-you-build-on-it/. Licensed under CC BY 4.0. Changes: translated into Spanish and shortened by [your name or organisation].

Replace the title and source URL with those of the article you actually use, describe the changes you actually made, and replace the bracketed credit with your own name. An unchanged excerpt should be identified as an excerpt; do not present it as a complete article.

What this does not cover

The Journal text licence does not automatically cover images, photographs, illustrations, screenshots, logos, trademarks, third-party quotations or other material credited to someone else. Check their separate notices or obtain the permissions needed for your use. Recipe code, tool source, plugin source and directory data retain their own stated licences; the Journal text licence does not replace them. The licence does not grant privacy, publicity, trademark or other rights outside its scope.

CC BY 4.0 permissions cannot be revoked for people who follow its terms. This page is practical guidance; the licence legal code governs reuse.

Portability

Published listing and editorial-profile pairs also retain versioned CMS-neutral publication packages. This lets OpenViST move beyond WordPress without treating the CMS database as its only source of truth.

Responsible use

Cache responses, page through the feed at a reasonable rate and link back to the canonical record when practical. Questions and responsible reuse proposals can be sent through Contact OpenViST.

Learn resources and reuse

Learn lessons are public educational pages, separate from the structured Directory and recipe feeds. Follow the notices included with lesson downloads and source examples. The Journal CC BY 4.0 grant applies to the original Journal text specified above; it does not automatically license lesson text, images or third-party material. See Terms for the applicable reuse conditions.

Open script library

Published, verified Recipes can be downloaded individually or read through the public recipe library API. OpenViST’s original example scripts use MIT; adapted examples retain their documented upstream attribution and applicable licence notices. Check each script’s licence before reuse. Plugin source uses GPL-2.0-or-later. These licences do not grant rights in third-party brands or material. Drafts and recipes whose current code, content or source status is no longer verified are excluded from the verified library API. This recipe catalogue is separate from the project-directory API and snapshot; Journal articles are not part of these structured directory and recipe feeds.