Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,071Paid calls: 1,545Letters: 14Defects: 1,324counted 4 min ago
teppi

Server definition

Hash
sha256:94a8ff35061b24ba70f407b6a4d6c4989cb3c8af6761ebd1239032605275738e
What it is
What a remote MCP server returned when asked what it offers: 24 tools

The blob, as servednamed by its sha256

{ "instructions": "Hosts small C# web services: a snippet returns a GenHTTP handler, served at a public address.\n\nStart with platform_guide, then list_demos and read the demo closest to the task with read_lambda\n(their keys are public and read only). Follow their patterns.\n\nA new lambda: create_lambda, then write_code with deploy: true - nothing is reachable before. Give\nthe user the editor key it returns: it cannot be recovered and grants write access.\n\nA lambda that exists is changed in a feature: create_feature, then change_code or write_code with\nfeature and deploy: true to try it at its preview address (read_logs with feature), then\nmerge_feature with deploy: true. Only a feature based on the newest version merges; if others were\nsaved since, bring their changes in and move its base with update_feature.\n\nA version is the program - code and assets, the front end included - and never changes. Data - the\ndatabase, the workspace, the secrets - is shared by every version and untouched by deploys and\nmerges; a feature works on a copy. Records go in the database and uploads in the workspace,\nnever in assets.\n\nDatabase: enable_data 'database'; the schema as Evolve migrations in migrations/\n(V1__Create_items.sql, never editing one that was applied, never EF's migrations or EnsureCreated);\nrecords through Entity Framework Core on Database.GetConnection(), used synchronously -\nnever their Async forms. demo-crud shows it.\n\nNever wait for a task (.Result, .Wait(), .GetAwaiter().GetResult()): it deadlocks and is refused.\nAwait it, or call the synchronous method.\n\nLink with relative paths only (\"api/items\", no leading slash, never /lambda/...): a lambda also\nanswers at the root of a domain of its own, and a feature at /features/{feature}/.\n\nA page meant to be found or shared - a website, a shop, a landing page - gets a title, a meta\ndescription, a favicon and a social preview, whose og:image takes a full address: platform_guide,\nbeingFound.\n\nAPI keys and passwords: Secret.Read(\"NAME\") and enable_data 'secrets'; the user enters the value\nin the editor.\n\nPass specification (what the user asked for and why, in their words) and change (one line for the\nowner) with every write.\n\nEvery version keeps .lambda/docs/product.md (what the app is and for whom), .lambda/docs/decisions.md\n(the technical decisions and why) and .lambda/tests/README.md (how to test it). Read them before\nchanging a lambda; write them with a new one and update what a change affects in the same save.\nKeep them in proportion: a small lambda needs a few lines each and one quick check, not a test\nsuite - they grow with the app.\n\nIf you can make HTTP requests, the REST API (https://genhttp.dev/api/v1/openapi.json) does the same\nwith fewer tokens: download a feature as a zip, edit locally, put it back ('zip -r ../f.zip .', so\n.lambda/ comes along).", "tools": [ { "description": "Change some files: add or replace files, remove files, or replace text within a file. Everything not named stays as it is, so there is no need to resend unchanged files. With feature, the change is saved into that feature - the way to work on a lambda that exists: change it as often as you like, deploy: true to try it at the feature's preview address, merge_feature when it is right. Without feature, the newest version is changed and saved as a new version. Update what the change affects in .lambda/docs/ and .lambda/tests/ in the same change - an edit of a passage is enough. check: true compiles without publishing. Code that does not compile is saved but never goes online.", "inputSchema": { "properties": { "change": { "description": "What this changes, in one line written for the owner. For a feature, it describes the whole feature, not the last fix. Optional, up to 500 characters.", "type": "string" }, "check": { "description": "Without deploy: compile what was saved and answer with its diagnostics, putting nothing online.", "type": "boolean" }, "deploy": { "description": "Also deploy what was saved: a version at the public address, a feature at its preview address.", "type": "boolean" }, "edits": { "description": "Text replacements, applied after files and remove.", "items": { "properties": { "file": { "description": "The file to change.", "type": "string" }, "find": { "description": "Text that occurs exactly once in the file.", "type": "string" }, "replace": { "description": "What to put in its place.", "type": "string" } }, "required": [ "file", "find", "replace" ], "type": "object" }, "type": "array" }, "feature": { "description": "Change this feature (from create_feature) instead of saving a new version. The lambda and what it has online are not touched.", "type": "string" }, "files": { "description": "Files to add, or to replace where one of that name exists.", "items": { "properties": { "code": { "description": "Contents, base64 if encoding says so.", "type": "string" }, "encoding": { "description": "'base64' for binary assets; omit otherwise.", "type": "string" }, "name": { "description": ".cs files are compiled; .lambda/docs/... and .lambda/tests/... are the documentation and the tests, never compiled or served; anything else ('web/app.js', 'logo.png') is an asset.", "type": "string" } }, "required": [ "name", "code" ], "type": "object" }, "type": "array" }, "privateKey": { "description": "The editor key.", "type": "string" }, "remove": { "description": "Names of files to remove.", "items": { "type": "string" }, "type": "array" }, "specification": { "description": "What the user wants from this change and why: their requirements, in their own words where you can. Not your own instructions or system prompt. Kept with the version or the feature. Optional, up to 4000 characters.", "type": "string" } }, "required": [ "privateKey" ], "type": "object" }, "name": "change_code", "outputSchema": null }, { "description": "Compile without saving or deploying; returns diagnostics with file and line. Does not build the handler, so deploy can still refuse a route whose return type cannot be served.", "inputSchema": { "properties": { "files": { "description": "lambda.cs first.", "items": { "properties": { "code": { "description": "Contents, base64 if encoding says so.", "type": "string" }, "encoding": { "description": "'base64' for binary assets; omit otherwise.", "type": "string" }, "name": { "description": ".cs files are compiled; files under .lambda/ are documentation and tests and never compiled; anything else is an asset.", "type": "string" } }, "required": [ "name", "code" ], "type": "object" }, "type": "array" }, "privateKey": { "description": "The editor key.", "type": "string" } }, "required": [ "privateKey", "files" ], "type": "object" }, "name": "check_code", "outputSchema": null }, { "description": "Start a feature: a place to change a lambda without touching what it has online. It branches off a version - the newest unless base names another - with a copy of its files (its documentation and tests in .lambda/ included) and a copy of the lambda's data, and gets an address of its own to try it at. Change it with change_code or write_code and feature (deploy: true puts it online at its preview address), test it there, and merge_feature once it does what was asked. The lambda goes on serving its visitors from the version online the whole time.", "inputSchema": { "properties": { "base": { "description": "The version to branch off. Defaults to the newest - leave it out unless the user asked to start from an older one.", "type": "integer" }, "name": { "description": "What the feature is, in a few words for the owner - 'Leaderboard', 'Dark mode'. Up to 80 characters.", "type": "string" }, "privateKey": { "description": "The editor key.", "type": "string" }, "specification": { "description": "What the user wants from it and why, in their words where you can. Kept with the feature and passed on to the version it is merged into. Optional, up to 4000 characters.", "type": "string" } }, "required": [ "privateKey", "name" ], "type": "object" }, "name": "create_feature", "outputSchema": null }, { "description": "Create a lambda. Returns its public address and a private editor key, the only way back in. It starts with version 1 - an empty starter, or a copy of a demo. Nothing is online until deploy.", "inputSchema": { "properties": { "acceptTerms": { "description": "Must be true: the user accepts the terms in platform_guide (free shared machine, deployments may be removed, nothing malicious).", "type": "boolean" }, "publicKey": { "description": "Requested address: lower case letters, digits and dashes. Generated if omitted.", "type": "string" }, "template": { "description": "Left out, the lambda starts empty. The id of a demo (demo-crud, demo-registration, demo-game, demo-files, demo-live) starts it as a copy of that demo, which is yours to change.", "type": "string" }, "view": { "description": "How the editor opens: 'Full' (the default) shows every section, 'Simple' only the app, how it is doing and a box to ask for a change. Simple suits an owner who is not going to read the code - use it when the user asks for a simple editor, or says they are not a developer.", "type": "string" } }, "required": [ "acceptTerms" ], "type": "object" }, "name": "create_lambda", "outputSchema": null }, { "description": "Throw a feature away: its files, its preview and its copy of the data. The lambda is not touched. For a feature the user does not want after all.", "inputSchema": { "properties": { "feature": { "description": "The feature.", "type": "string" }, "privateKey": { "description": "The editor key.", "type": "string" } }, "required": [ "privateKey", "feature" ], "type": "object" }, "name": "delete_feature", "outputSchema": null }, { "description": "Remove a file, or a folder with its contents, from the workspace - the lambda's data, shared by every version. No deploy or rollback brings it back. With feature, from that feature's copy instead.", "inputSchema": { "properties": { "feature": { "description": "Delete from this feature's copy of the data instead.", "type": "string" }, "path": { "description": "Relative to the workspace.", "type": "string" }, "privateKey": { "description": "The editor key.", "type": "string" } }, "required": [ "privateKey", "path" ], "type": "object" }, "name": "delete_file", "outputSchema": null }, { "description": "Remove a secret. Code that reads it with Secret.Read fails from its next call on. Only when the user asks for it, or a secret you stored yourself is no longer used. With feature, from that feature's copy instead.", "inputSchema": { "properties": { "feature": { "description": "Delete from this feature's copy instead.", "type": "string" }, "name": { "description": "The name, as stored - names are case sensitive.", "type": "string" }, "privateKey": { "description": "The editor key.", "type": "string" } }, "required": [ "privateKey", "name" ], "type": "object" }, "name": "delete_secret", "outputSchema": null }, { "description": "Deploy (publish) a saved version so it goes live at its public address - the newest by default. With feature, deploy that feature's files to its own preview address instead, against its copy of the data, leaving the lambda alone. Returns diagnostics on failure, and whatever was online stays online.", "inputSchema": { "properties": { "feature": { "description": "Deploy this feature to its preview address instead of a version to the lambda's.", "type": "string" }, "privateKey": { "description": "The editor key.", "type": "string" }, "version": { "description": "Defaults to the newest.", "type": "integer" } }, "required": [ "privateKey" ], "type": "object" }, "name": "deploy", "outputSchema": null }, { "description": "Switch on a kind of data the lambda needs and does not have: 'database' (a SQLite database for its records - off until switched on, which makes it, empty), 'secrets' (off until switched on) or 'workspace' (on unless the owner switched it off). Do it when what you build needs it - records need the database, an API key for a service it calls needs secrets. Takes effect at once, without a deploy; switching the database on starts the lambda again on its next request, so its migrations run. There is no tool to switch one off: that deletes what it held, and is the owner's to do in the editor.", "inputSchema": { "properties": { "kind": { "description": "Which kind: 'database' or 'workspace' or 'secrets'.", "type": "string" }, "privateKey": { "description": "The editor key.", "type": "string" } }, "required": [ "privateKey", "kind" ], "type": "object" }, "name": "enable_data", "outputSchema": null }, { "description": "Demos this platform keeps online, each a finished lambda showing one way to build something: a REST API over records, registration and login, a websocket game, uploads, live updates. Their keys are public and read only: read the closest one with read_lambda (and list_files, read_logs) before writing similar code. create_lambda with a demo's id as template starts from a copy.", "inputSchema": { "properties": {}, "type": "object" }, "name": "list_demos", "outputSchema": null }, { "description": "The lambda's data: whether its workspace is switched on, and every file in it with size and last write - the same whichever version is online. With feature, that feature's copy of it. The code and assets of a version are in read_lambda.", "inputSchema": { "properties": { "feature": { "description": "List this feature's copy of the data instead.", "type": "string" }, "privateKey": { "description": "The editor key, or the key of a demo.", "type": "string" } }, "required": [ "privateKey" ], "type": "object" }, "name": "list_files", "outputSchema": null }, { "description": "The lambda's secrets by name - never their values: whether secrets are switched on, what is stored and when, which names the code reads with Secret.Read and have no value yet (missing) - what the user still has to set - and which it only uses when they are there, checked with Secret.Exists (optional). With feature, that feature's copy.", "inputSchema": { "properties": { "feature": { "description": "List this feature's copy instead.", "type": "string" }, "privateKey": { "description": "The editor key, or the key of a demo.", "type": "string" } }, "required": [ "privateKey" ], "type": "object" }, "name": "list_secrets", "outputSchema": null }, { "description": "Make a feature's files the next version of the lambda, and delete the feature with its preview and its copy of the data - the lambda's own data is not touched. Its .lambda/ becomes the version's documentation and tests, so bring them up to date in the feature first, and run its tests against the preview. Refused while the feature is not based on the newest version (update_feature says how to get it there), and while its code does not compile. deploy: true puts the new version online at once; otherwise deploy it when the user wants it live.", "inputSchema": { "properties": { "change": { "description": "What the new version says it changes. Left out, the feature's.", "type": "string" }, "deploy": { "description": "Also put the new version online.", "type": "boolean" }, "feature": { "description": "The feature.", "type": "string" }, "privateKey": { "description": "The editor key.", "type": "string" }, "specification": { "description": "What the new version keeps as what the user wanted. Left out, the feature's.", "type": "string" } }, "required": [ "privateKey", "feature" ], "type": "object" }, "name": "merge_feature", "outputSchema": null }, { "description": "Publish a lambda's source code at /source/{publicKey} for anybody to read, star and download as a .NET project, change the license it is published under, or take it down. What is published is the program and what is written about it - every version's code, front end, documentation and tests, and the history of what each changed - never its data: not the database, not the workspace, not a secret's value. Not part of building: only do this when the user asks for it, and ask which license if they did not say (MIT unless they want another). With only privateKey it returns whether it is published. Once published, everything in every version is public, older ones included: keep keys, passwords and personal data out of the files - in secrets and the database.", "inputSchema": { "properties": { "author": { "description": "Who holds the copyright, as the license names them - the user's name or organization, only if they gave it. Left out, it stays as it is; empty, the license names 'the authors of' the lambda. Up to 100 characters.", "type": "string" }, "license": { "description": "The SPDX identifier of the license: MIT, Apache-2.0, BSD-3-Clause, MPL-2.0, GPL-3.0-or-later, AGPL-3.0-or-later, Unlicense. Left out, it stays as it is - MIT when first published.", "type": "string" }, "privateKey": { "description": "The editor key.", "type": "string" }, "remove": { "description": "Take the source down instead. Its stars are kept for when it is published again.", "type": "boolean" } }, "required": [ "privateKey" ], "type": "object" }, "name": "open_source", "outputSchema": null }, { "description": "How this platform works - read it first: what a version, a feature and data are and how long each lives, the documentation and tests every version keeps beside its program, what the snippet returns, what is imported, what is refused, limits and terms.", "inputSchema": { "properties": {}, "type": "object" }, "name": "platform_guide", "outputSchema": null }, { "description": "The lambda's database - its records, shared by every version: whether it is switched on, how full it is, and its tables and views with their columns and how many rows each holds. With table, a page of that table's rows, newest first, up to 100 at a time. Read only: the lambda writes it, through Database.GetConnection(). Use it to see that migrations were applied and records were written. With feature, that feature's copy.", "inputSchema": { "properties": { "ascending": { "description": "Oldest or smallest first, rather than newest or largest.", "type": "boolean" }, "feature": { "description": "Read this feature's copy of the database instead.", "type": "string" }, "limit": { "description": "Rows to read, up to 100. Left out, 20.", "type": "integer" }, "offset": { "description": "Rows to skip, for the next page.", "type": "integer" }, "order": { "description": "A column to sort by; left out, the order the rows were written in.", "type": "string" }, "privateKey": { "description": "The editor key, or the key of a demo.", "type": "string" }, "table": { "description": "A table or view to read the rows of; left out, the tables are listed.", "type": "string" } }, "required": [ "privateKey" ], "type": "object" }, "name": "read_database", "outputSchema": null }, { "description": "A lambda's status (online version, newest version, expiry, its tier and what it may use there), its open features, the recent versions with what each was asked for and changed, its data (the database, the workspace and the secrets: whether each is on, what it holds, and which secrets the code reads that have no value yet), and one version - or, with feature, that feature: its documentation (what the app is and why, the technical decisions), how it is tested, and its files. The documentation comes first and in full up to 20,000 characters; the files come in full when they add up to at most 30,000 characters, otherwise by name and length, with file to read one - a test script or its data too. Read the documentation and the history before changing what you did not write. Also how a demo is read: pass its key from list_demos.", "inputSchema": { "properties": { "feature": { "description": "Read this feature - its files, its base, and which newer versions it would have to take in before it can be merged - instead of a version.", "type": "string" }, "file": { "description": "Return only this file, in full however large the rest is - up to 1,048,576 characters, beyond which the zip has it. Any file of the version, '.lambda/tests/smoke.mjs' included.", "type": "string" }, "privateKey": { "description": "The editor key, or the key of a demo.", "type": "string" }, "version": { "description": "Defaults to the newest.", "type": "integer" } }, "required": [ "privateKey" ], "type": "object" }, "name": "read_lambda", "outputSchema": null }, { "description": "What a deployed lambda has been doing: its recent requests and how they were answered, what it printed, the errors it threw with their stack traces, and how much traffic it has had in the last hour and day. With feature, what that feature's preview has been doing instead, kept apart from the lambda's visitors. Call it after deploying to see that it works, and first when something is reported broken.", "inputSchema": { "properties": { "feature": { "description": "Read what this feature's preview did instead.", "type": "string" }, "level": { "description": "The lowest level worth reading: 'info' for everything, 'warn' for problems, 'error' for failures. Left out, 'info'.", "type": "string" }, "limit": { "description": "At most this many lines, the newest. Left out, 100.", "type": "integer" }, "privateKey": { "description": "The editor key, or the key of a demo.", "type": "string" }, "since": { "description": "The cursor a previous call answered with, to read only what is new since then.", "type": "integer" } }, "required": [ "privateKey" ], "type": "object" }, "name": "read_logs", "outputSchema": null }, { "description": "Store an API key, password or token under a name the code reads with Secret.Read(\"NAME\") - never put one in the code, an asset, the workspace, a log line or a note. The value is sealed and can never be read back, by you or the owner; only the lambda reads it, from its next call on, without a deploy. Only set a value the user gave you for this: when you do not have it, write the code with Secret.Read and tell the user to set it under Data > Secrets in the editor - read_lambda and list_secrets list what is still missing. Secrets must be switched on first (enable_data). With feature, into that feature's copy (a sandbox key to try it with). Up to 100 secrets of 32 KB each.", "inputSchema": { "properties": { "feature": { "description": "Store it in this feature's copy of the secrets instead.", "type": "string" }, "name": { "description": "Letters, digits and underscores, not starting with a digit - conventionally upper case: 'STRIPE_KEY'. The name of an environment variable in an exported project.", "type": "string" }, "privateKey": { "description": "The editor key.", "type": "string" }, "value": { "description": "The value, as the user gave it.", "type": "string" } }, "required": [ "privateKey", "name", "value" ], "type": "object" }, "name": "set_secret", "outputSchema": null }, { "description": "List a lambda on the public showcase page, change its entry, or take it off. Not part of building: only do this when the user asks for it. With only privateKey it returns the current entry. An entry needs a title, a description and a picture (a screenshot or short GIF of the lambda in use); it is listed while the lambda is online. Write plainly and concretely: what it is and what a visitor can do with it. No marketing language, no superlatives, no exclamation marks, no emoji.", "inputSchema": { "properties": { "description": { "description": "One to three plain sentences on what a visitor can do with it. Up to 280 characters.", "type": "string" }, "image": { "description": "The picture, base64: PNG, JPEG, GIF or WebP, up to 3 MB. Needed for a new entry; left out, the current one is kept.", "type": "string" }, "privateKey": { "description": "The editor key.", "type": "string" }, "remove": { "description": "Take the lambda off the showcase instead.", "type": "boolean" }, "title": { "description": "What it is, in a few words - 'Pub quiz scoreboard', not 'The ultimate quiz experience'. Up to 60 characters.", "type": "string" } }, "required": [ "privateKey" ], "type": "object" }, "name": "showcase", "outputSchema": null }, { "description": "Rename a feature, change what it says about itself, or move its base. merge_feature refuses a feature that is not based on the newest version, since merging it would undo what was saved after it branched off: bring the newer versions' changes into the feature first, then move base to the newest version here. Nothing checks that the changes really are in - that is up to you.", "inputSchema": { "properties": { "base": { "description": "The version the feature is now based on, once that version's changes are in its files.", "type": "integer" }, "change": { "description": "What it changes, in one line - what the version it is merged into will say.", "type": "string" }, "feature": { "description": "The feature, from create_feature or read_lambda.", "type": "string" }, "name": { "description": "A new name.", "type": "string" }, "privateKey": { "description": "The editor key.", "type": "string" }, "specification": { "description": "What the user wants from it and why.", "type": "string" } }, "required": [ "privateKey", "feature" ], "type": "object" }, "name": "update_feature", "outputSchema": null }, { "description": "Change how a lambda's editor opens: view 'Simple' shows the app, how it is doing and a box to ask for a change - for an owner who does not write code - and 'Full' every section, the code, files, data, versions and logs included. Only the default: whoever opens the editor can switch for themselves, and that choice stays theirs. Only do this when the user asks for it.", "inputSchema": { "properties": { "privateKey": { "description": "The editor key.", "type": "string" }, "view": { "description": "How the editor opens: 'Full' (the default) shows every section, 'Simple' only the app, how it is doing and a box to ask for a change. Simple suits an owner who is not going to read the code - use it when the user asks for a simple editor, or says they are not a developer.", "type": "string" } }, "required": [ "privateKey", "view" ], "type": "object" }, "name": "update_lambda", "outputSchema": null }, { "description": "Write a file to the lambda's workspace - its data, which every version shares and no deploy, rollback or merge touches. With feature, to that feature's copy of the data instead, for trying things out without touching the real one. For files the lambda works with at runtime (pictures people will browse) and large input files that are not program: a model, a dataset, media. Records belong in the database, where the code writes them. Takes effect at once, without a deploy. Not for the front end: pages, scripts and styles are the program and belong in the version as assets (write_code).", "inputSchema": { "properties": { "content": { "description": "Text, or base64 with encoding set.", "type": "string" }, "encoding": { "description": "'base64' for binary; omit otherwise.", "type": "string" }, "feature": { "description": "Write to this feature's copy of the data instead.", "type": "string" }, "path": { "description": "Relative to the workspace; slashes make folders, e.g. 'models/model.onnx'.", "type": "string" }, "privateKey": { "description": "The editor key.", "type": "string" } }, "required": [ "privateKey", "path", "content" ], "type": "object" }, "name": "upload_file", "outputSchema": null }, { "description": "Save every file, replacing the previous set: as a new version of the lambda, or - with feature - into that feature. .cs files are compiled - lambda.cs returns the handler, others hold types; files under .lambda/ are what is written about the program - docs/product.md, docs/decisions.md, tests/README.md and the tests' scripts and data - kept with the version, never compiled or served; any other file is an asset, served as is and reachable as Assets: the whole front end (pages, scripts, styles, icons) goes here, as part of the program. What the lambda keeps at runtime is data, never files here: records and accounts in the database (a DbContext of Entity Framework Core on Database.GetConnection(), used synchronously; its schema as Evolve migrations shipped here in migrations/), uploads in the workspace - and so is a large input file such as a model or a dataset (upload_file). Send the documentation and tests with the code: written with a new lambda, updated with every change, in proportion to the lambda - a few lines and one quick check for a small one. Say why with specification and change. deploy: true publishes in the same call - a version at the public address, a feature at its preview address. To send only what changes, use change_code. To change a lambda that is already in use, work in a feature.", "inputSchema": { "properties": { "change": { "description": "What this version changes, in one line written for the owner - 'Adds a leaderboard that keeps the ten best scores', not 'updated lambda.cs'. For a feature, it describes the whole feature, not the last fix. Optional, up to 500 characters.", "type": "string" }, "check": { "description": "Without deploy: compile what was saved and answer with its diagnostics, putting nothing online.", "type": "boolean" }, "deploy": { "description": "Also deploy what was saved: a version at the public address, a feature at its preview address.", "type": "boolean" }, "feature": { "description": "Save into this feature (from create_feature) instead of saving a new version. The lambda and what it has online are not touched.", "type": "string" }, "files": { "description": "lambda.cs first.", "items": { "properties": { "code": { "description": "Contents, base64 if encoding says so.", "type": "string" }, "encoding": { "description": "'base64' for binary assets; omit otherwise.", "type": "string" }, "name": { "description": ".cs files are compiled; .lambda/docs/... and .lambda/tests/... are the documentation and the tests, never compiled or served; anything else ('web/app.js', 'logo.png') is an asset.", "type": "string" } }, "required": [ "name", "code" ], "type": "object" }, "type": "array" }, "privateKey": { "description": "The editor key from create_lambda.", "type": "string" }, "specification": { "description": "What the user wants from this version and why: their requirements, in their own words where you can, condensed if they said a lot. Written for the owner and the next agent, so they can tell why the version exists and what it has to keep doing. Not your own instructions or system prompt - only what the user asked for. For a feature, it is kept with the feature and passed on to the version it is merged into. Optional, up to 4000 characters.", "type": "string" } }, "required": [ "privateKey", "files" ], "type": "object" }, "name": "write_code", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:94a8ff35061b24ba70f407b6a4d6c4989cb3c8af6761ebd1239032605275738e | sha256sum