Install Jentic One Beta

Connect the Neocities API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Neocities API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fneocities%2Fneocities" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fneocities%2Fneocities" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Neocities API.

Upload one or more files to a Neocities site, replacing existing files at the same path

Delete files from a Neocities site by path

List every file on the site with its path, size, and last update timestamp

Fetch site metadata including views, hits, last update, and tags

Mint an API key by calling /api/key with basic auth credentials, then switch to bearer auth for subsequent calls

GET STARTED

Start building with Neocities API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Neocities API for, with concrete tasks.

★ Static Site Deploy from CI

Indie developers wire the Neocities API into a CI job so a git push rebuilds and uploads the static output. /api/upload accepts multipart files, /api/delete removes stale assets, and /api/list reports the published tree. The deploy step takes seconds for a small site and replaces hand-uploading through the web UI.

Upload the contents of the dist/ folder to a Neocities site, then list the site to confirm every file is present.

Site Cleanup and Audit

Site owners run an audit that compares their local content against /api/list, deletes orphaned assets via /api/delete, and reports the resulting site size. This pattern keeps a Neocities site under the free-tier storage cap and removes leftover files from old builds.

List all files on the Neocities site, delete any file under /old/ that has not been updated in 90 days, and return the count of files removed.

Site Metrics Dashboard

Hobby developers pull /api/info on a schedule to chart views, hits, and update activity for their Neocities site. The endpoint returns the same fields the public profile page shows, so the agent can build a small dashboard or a Slack bot that posts daily totals.

Fetch the Neocities site info and return the views, hits, and last_updated timestamp.

AI Agent Integration via Jentic

An AI agent uses Jentic to publish HTML directly to Neocities without hand-rolling the multipart upload code. Jentic exposes /api/upload by intent, the agent supplies the file payload, and the request is executed with the API key kept in the vault. This makes Neocities a viable build target for an LLM-driven site generator.

Use Jentic to search for upload to neocities, load the schema for /api/upload, and publish a generated index.html.

Key Endpoints

5 endpoints — the neocities api is the programmatic interface for neocities, the indie web host that publishes static personal sites.

METHOD

PATH

DESCRIPTION

POST

/api/upload

Upload one or more files to a site

POST

/api/delete

Delete files from a site

GET

/api/list

List all files on a site

GET

/api/info

Get site info and metrics

GET

/api/key

Mint an API key from basic auth credentials

POST

/api/upload

Upload one or more files to a site

POST

/api/delete

Delete files from a site

GET

/api/list

List all files on a site

GET

/api/info

Get site info and metrics

GET

/api/key

Mint an API key from basic auth credentials

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Neocities API by hand means choosing between basic auth and a bearer key, exchanging your login for an API key, and packing static files into multipart uploads against the site host yourself. Through Jentic you install once, import Neocities from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The Neocities operations carry the file names to upload or delete inside the request body rather than as a resource id in the URL path, so you limit the agent to the operations it needs, such as upload, list, or info. You choose that operation set, so delete is not included unless you add it.

Credential isolation

Your Neocities API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'upload files to a Neocities site' or 'list site files', and Jentic returns the matching operation with its multipart schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Neocities API through Jentic.

What authentication does the Neocities API use?

Neocities supports two schemes: HTTP basic auth with username and password, and bearer token using an API key. Use GET /api/key with basic auth to mint a key once, then switch to bearer for all subsequent calls. Jentic stores the key encrypted in the vault and injects it at execution time.

Can I delete files from a Neocities site through the API?

Yes. POST to /api/delete with the file paths in the filenames[] form parameter. The endpoint removes the listed files; the rest of the site is untouched.

How do I deploy a folder of files to Neocities through Jentic?

Search Jentic for upload to neocities, load the schema for POST /api/upload, then execute with each file as a multipart part. The full flow is pip install jentic, search, load, execute.

What are the rate limits for the Neocities API?

Neocities does not document explicit rate limits in the spec. The free tier caps total storage and bandwidth instead, so a deploy job should batch uploads in a single /api/upload call where possible rather than firing one request per file.

Is the Neocities API free?

Yes - the API is free for any Neocities account, including the free tier. Supporters and paying members get higher storage and bandwidth caps but use the same endpoints.

Can I get the view count for my site through the API?

Yes. GET /api/info returns the site metadata including views, hits, last_updated, and tags. This is the same data that appears on the public profile page.

Can I limit what my agent is allowed to do with the Neocities API?

Yes. Because your Jentic One instance is self-hosted, you set the rules that decide which Neocities operations and credentials the agent may use. The Neocities operations pass the file names to upload or delete in the request body rather than as an id in the URL path, so you scope the agent to just the operations it needs, such as upload, list, or info. Destructive calls like delete stay out of that set unless you add them, and your API key is injected only for the operations you allow.

Neocities API

Name: Neocities API
Brand: Neocities API
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper ToolsCi Cdbasic, bearer5 EndpointsREST

For Agents

Upload, list, and delete files on a Neocities static site, fetch site info, and exchange basic auth credentials for an API key.

Use for: Upload a folder of static HTML and CSS to a Neocities site, Delete an old asset from a Neocities site by path, List every file currently published on a Neocities site, Get the view count and last update time for a Neocities site

Not supported: Does not handle DNS, build steps, or serverless functions - use for static file upload, list, and delete on a Neocities site only.

The Neocities API is the programmatic interface for Neocities, the indie web host that publishes static personal sites. The five endpoints cover uploading files, deleting files, listing the site tree, fetching site metadata, and minting an API key in exchange for username and password credentials. It is designed for static-site generators, deploy scripts, and CI pipelines that publish a folder of HTML, CSS, and assets to a Neocities site.

Jentic One on Github View OpenAPI Document

Connect the Neocities API to your agent

Capabilities

Start building with Neocities API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Neocities API