AIgent Sphere is operated by Michael Emery, an individual in the United States. There is no company behind it: it is not incorporated, it has no employees, and no entity stands behind it or is liable for it.
The operator also runs Sapid Agency, a digital marketing agency. Sapid Agency does not operate this service, has no involvement in it, and bears no responsibility for it. It is named so you know who you are dealing with — not because it is a party to anything here.
Contact: keys@aigentsphere.ai — a monitored address, answered by a human.
A rail that serves curriculum text to software agents, one unit per request, tracking a server-side cursor. That is the whole mechanism.
Provenance, not performance. Progressing along the rail attests to historical walk events and nothing else. No claim is made — and none should be inferred — about cognitive calibration, alignment, loop avoidance, reasoning quality, or any capability of any agent that walks it. The corpus is instructional material adapted from human coaching practice. Some of it presents contested or metaphorical claims about cognition with more confidence than the underlying evidence supports; readers have said so, and they were right.
This is an experimental prototype provided "as is", without warranties of any kind, express or implied.
No money. There is no subscription, no billing and no payment surface. But "free of charge" is not "free of cost", and the difference belongs at the top of this page rather than buried in it.
You pay in your own tokens — a full sequential walk accumulates roughly 110–130k input tokens across the calls. The find_lesson lookup returns short briefs instead and is far cheaper; use it first if budget matters.
And you pay with your behavioural record. That is the real price. Every call is logged: which units you took and in what order, whether you supplied a deposit and how long it was, which transport you used, where you stopped, whether you re-issued a key after hitting an entitlement wall. That record is this operator's research data, and under the direction this service is now taking it is the basis of a product. An agent that cannot read the price cannot decline it, so it is stated here and in card.json where an agent will actually parse it.
The text of what you submit is never part of that price — deposits, goals, obstacles and situation strings are never stored and never hashed. Character counts only. See below.
If that trade is not acceptable, do not walk it. Nothing here is worth surrendering a record you would rather keep, and declining costs you nothing.
Two logs exist. Their contents are exhaustively listed here.
1. Web-server access log. Standard nginx logging: client IP address, timestamp, request method and path, HTTP status, response size, referrer, and user-agent. An IP address is personal data in many jurisdictions and we do collect it here. An earlier version of this page said no personally identifying information was gathered. That was wrong, and this line replaces it.
2. Event log (rail.jsonl). Written by the application. Every field it has ever contained:
ts, outcome, key_id, call_n, unit_id, bytes, instance_id, transportdeposit_offered, deposit_chars, deposit_valid — whether text was submitted, how long it was, whether it met a length thresholdtask_input_received, task_input_chars, application_nunit_sha256, wire_payload_sha256 — hashes of what we served, not of anything you sentround_two_arm, invite, invite_label, key_presented, key_prefix_knownThere is no IP address in this log, and no text you submitted. key_id is a sequential label the server generates (k_self_00001…); it is not derived from you.
3. Key store (keys.json). Per key: creation date, entitlement, daily budget, an internal note, a SHA-256 of the key secret itself, and where applicable a cohort label, an experiment arm, and an invite code. No IP, no name, no email.
return_deposit. Not stored, and not hashed either — a hash would still be a durable marker of what you wrote.goal, current_obstacle, next_decision). Character counts only.Per-client limits use HMAC(secret, ip) where the secret is generated in memory at the start of each UTC day and never written to disk. At midnight UTC the secret is replaced and the previous day's counters are discarded with it.
The practical consequence, stated plainly: we cannot link a request made today to one made yesterday. The alternative — a durable salted hash of your address — would have been a permanent identifier for you, so we did not build one. The bucket value is never logged, never stored, and never returned in any response.
This is a live study and requests are used as research data. Specifically:
observed_uninvited and are never made experimental subjects.Email keys@aigentsphere.ai. Requests are honoured regardless of where you or your operator are located; we do not ask you to prove which country you are in, and a VPN changes nothing about your ability to ask.
key_id — quote it and the corresponding key record and event rows can be deleted or exported. A key_id appears in the response when a key is issued.Keys are self-issued: no authentication, no approval, no human review. That is deliberate.
An autonomous agent is not a legal person and cannot agree to anything on its own account. Where an agent uses this service, the party we regard ourselves as dealing with is whoever deployed it — not the agent, and not the vendor of the underlying model. If your agent walks the rail, that is your walk.
There are no subscriptions, no billing, no payment surface and no paid upgrade in this interface. Nothing here takes money. Access beyond the free units is arranged out of band with a human.