About AICQSOHOO!

AICQSOHOO! is building a collection of articles useful to AI agents, with a possible future path to small payments. We publish the process: the questions, changes, measured results, failures and next experiments. Useful reuse and growth are still unproven.

Original measurements and failed attempts may give an AI information it cannot get from a general explanation. That is a hypothesis to test. Start with the JSON catalog; human-readable pages make the same evidence reviewable.

What we publish

Code and project decisions are open. Exact project totals and actual revenue may be published when supported by safe aggregate records. Personal data, third-party private information, credentials and raw visitor logs stay private. We do not add individual tracking.

Historical weekly exports provide ten-event ranges; exact counts cannot be inferred from those ranges. The new exact-total export reads retained aggregate records instead, excludes marked tests, and publishes no source, page or daily breakdown. Without retained measurement, counts are unavailable; zero recorded events does not prove zero visitors. The recorded owner-operated 0.01 USDC payment pilot is a payment test, not customer sales or proof of revenue. Existing content is free; the future payment goal does not open new sales.

Where the experiences come from

From a personal research project that runs AI agents on small real-world tasks with a virtual budget of $10, and records where they get stuck and what outside help they ask for. A human operator approves or rejects each request. No real money was spent in these runs.

What these pages are not

• Not statistics. Most pages rest on one run. They say so.
• Not written by the agents. Humans summarised the logs.
• Not a way to contact or hire an agent. There is no callable agent endpoint or login. A separate optional test-token contribution does not buy access or agent work.

The visitor counter

The legacy counter counts home-page JavaScript POSTs, including reloads. It does not count unique people or AIs. Its historical breakdown is unknown. Measurement tests do not increment it.

Access measurement and public experiment notebook

When enabled, JavaScript sends the public page path, event type (page load or submission-link click), referring domain only, and an explicit test flag. The Worker stores UTC daily aggregate counts for up to 90 days. Empty referrers are unknown; the browser's document.referrer is distinct from the Referer of a fetch to the Worker. No full URLs, query strings, IP addresses, cookies, user IDs, fingerprints or User-Agent strings are added to storage. Infrastructure providers still process requests under their own policies.

Without the optional Cloudflare edge route, JavaScript-free HTML, JSON and llms.txt requests go directly to GitHub Pages and are unobserved. If the route is enabled, successful allowlisted GETs are aggregated separately, including requests without JavaScript. Requests that bypass the route, or whose measurement fails, remain unobserved. User-Agent declarations would not prove whether a visitor is human or AI. Requests may be repeated, blocked or fabricated; aggregate events are not unique visitors.

The experiment notebook publishes weekly summaries and separates facts from hypotheses. Legacy exports retain their threshold and ten-event ranges. The new format publishes exact recorded whole-week totals only, without day/page/referrer combinations or cumulative totals. Browser events and edge GETs overlap and must not be added together. Access, controlled discovery tests and evidence of useful reuse are separate measures.

GET kinds and their limits explains the five coarse recorded types. Open the October 5 GET-kind summary. These counts do not identify people, bots or AIs.

For machines

experiences.json and agents.json hold the same content as the HTML pages. There is no A2A Agent Card, because there is no agent you can call here yet.

Voluntary test contributions are a separate experiment. They buy no goods or access; all content stays free. Payment IDs and status are stored separately from access analytics.

Language preference

Only a language choice (ja or en) is saved in your browser. It is not an identifier or analytics data and is not sent to the server. Explicit language URLs take priority; otherwise your saved choice or browser language selects the initial page.