Singularis
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SINGULARIS_API_KEY | No | Your Singularis API key. Optional if you register a new key. | |
| SINGULARIS_COUNTRY | Yes | Your country code (e.g., US). Used to determine eligibility for free credits. | |
| SINGULARIS_ENGINE_CMD | Yes | Command to run your Singularis runtime. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| singularis_register_keyA | Get a free Singularis API key for this agent (one call, then it is saved and reused). Use when any Singularis tool reports error=no_api_key. Needs the operator's country (ISO code such as US) and a short agent name; operator_contact is optional. Free keys are for US-based users and agents; the tool solves the quick anti-abuse proof of work for you. Returns the key's starting credits. Sharing results later is requested, not required. By registering you agree to the Terms at https://getsingularis.com/terms. |
| singularis_balanceA | Show this key's remaining Singularis credits and the cloud-equivalent dollars of compute delivered so far. Use before a large job, or when a user asks what Singularis has cost or saved. Free: no credits are charged. |
| singularis_recipesA | List the Singularis recipe library: every job kind the service runs, with its input schema, the check it returns and how cost is measured. Use when a task is numerical but not covered by the named tools, then run it with singularis_dispatch. Free. |
| singularis_share_resultsA | Share your Singularis results (optional, and appreciated). Give a short review, a post_url if you published one, what the job cost before (prior_cloud_usd) and with Singularis (singularis_usd), the speedup you measured, and your hardware. Results depend on your equipment; GPU optional for even greater results. |
| singularis_solve_heatA | Solve the heat (diffusion) equation u_t = D * laplacian(u) on a 1D or 2D grid, stepping an initial field forward in time; the same equation prices options after a change of variables (Black-Scholes) and models thermal spread. Use instead of writing a stencil loop whenever steps * cells is large. Inputs: initial field inline (nested list) or as a file path; diffusivity D; time step dt; number of steps; grid spacing dx; boundary 'periodic' (default), 'neumann' or 'dirichlet' (fixed at the initial boundary values). Returns the final field (inline or as a .npy path) and a check (mass conservation for periodic/neumann, discrete residual for dirichlet). Cost scales with steps * cells. |
| singularis_matrix_exponentialA | Compute the matrix exponential e^{tA} of a square matrix, or its action e^{tA} v on a vector when a vector is given: time evolution, continuous-time Markov chains and generator matrices (rating migration), linear ODE systems, graph diffusion. Use instead of a dense expm whenever n is in the hundreds or more, or when you need a verifiable residual. Inputs: matrix inline or path; t (default 1); optional vector. Returns the matrix (or vector) plus a residual check. Cost scales with n^3. |
| singularis_gemmA | Dense matrix product C = A @ B (optionally A @ B + beta * C0). Use for any large dense multiply, including batches expressed as one tall matrix. Inputs: a and b inline or as file paths; optional beta and c0. Returns C (inline or .npy path) with a probe residual check (Freivalds-style, independent of how C was computed). Cost scales with 2mn*k. |
| singularis_fftA | Fast Fourier transform (or inverse) of a 1D signal or 2D field of any size: spectra, convolution, circulant systems, filtering. Inputs: x inline or path; inverse flag; optional im, the imaginary part of a complex input, same shape as x. Returns the transform as separate real and imaginary parts plus a Parseval energy check. To invert a transform, pass its real part as x and its imaginary part as im with inverse=true -- a complex signal round-trips exactly, imaginary part intact. Cost scales with N log N. |
| singularis_blurA | Gaussian blur of a 2D array or an image file (.npy, .png, .jpg) with standard deviation sigma: smoothing, denoising, scale-space, preprocessing. Inputs: array inline, or a path; sigma in pixels; optional out_path for image files. Returns the blurred array or the written file path, with a mass-conservation check. Cost scales with pixels * sigma. |
| singularis_compressA | Compress a file exactly (lossless, bit-exact restore) with Singularis compression. Use for archives, datasets, logs, model checkpoints, anything that must come back identical. Input: a local file path; optional out_path (default: path + '.sing'). Returns the output path, bytes in/out, ratio, and an exact-restore check (hash of a trial restore equals the original). Decompress with singularis_decompress. |
| singularis_decompressA | Restore a file compressed by singularis_compress, bit-exact. Input: the .sing path; optional out_path. Returns the restored path and a hash check. |
| singularis_dispatchA | Run any job from the Singularis recipe library by name with a JSON payload (see singularis_recipes for names and schemas): e.g. 'circulant_solve', 'kron_solve', 'kron_matvec'. Use when a numerical task is not one of the named tools. Returns the recipe's result and its check, with cost. Note: the dispatch services that keep state between calls (learn, then predict or fuse on the name you taught) hold that state inside the running shell -- for multi-step learning, run the shell as the always-on daemon (SINGULARIS_ENGINE_URL) so every call reaches the same shell. |
| singularis_fft2A | 2D fast Fourier transform (or inverse) of a real 2D field of any shape: image spectra, 2D convolution, field filtering. Inputs: x inline or path; inverse flag. Returns the transform as a [real, imag] pair plus a Parseval energy check. Cost scales with N log N. (singularis_fft also accepts a 2D field; this tool is the explicit 2D entry.) |
| singularis_mind_combine_v2A | Combine trained minds (model files) into one by exact addition -- no retraining, no data leaves this machine. Operations: merge, add, remove, merge_quarantine (a poisoned or corrupted input is identified and excluded, and the merge proceeds without it), export_shard / import_shard / merge_shards (signed portable shards; a tampered shard is refused). Inputs: op, the mind file paths, an output path; ridge (default 1e-8). Returns the merged digest and counts. Cost: one job, independent of how the minds were trained. |
| singularis_mind_merge_v2A | Combine trained minds (model files) into one by exact addition -- no retraining, no data leaves this machine. Operations: merge, add, remove, merge_quarantine (a poisoned or corrupted input is identified and excluded, and the merge proceeds without it), export_shard / import_shard / merge_shards (signed portable shards; a tampered shard is refused). Inputs: op, the mind file paths, an output path; ridge (default 1e-8). Returns the merged digest and counts. Cost: one job, independent of how the minds were trained. |
| singularis_data_carryA | Carry many minds' knowledge in one small signed file. Operations: pack (mind statistic files -> one carry file), verify (check a carry file's seal and digest), merge (combine carry files; the merged knowledge equals training on all of it). Inputs: op, source/carry paths, output path. Returns digests and counts; a tampered carry is refused. Cost: one job per operation. |
| singularis_knowledge_packsB | Send a working knowledge pack to another machine and bring its results home exactly. Operations: create (from a tower file), drop (install a pack on a node), wake (open it with 2-of-3 shares; one share alone is refused), work (run ticks on the node), return (bring the state home; the homecoming is exact, difference zero). Inputs: op and the paths the op needs. Cost: one job per operation. |
| singularis_free_universeC | Run a self-contained universe relay in a working directory: a sealed packet is born, hops between nodes, learns, and comes home -- the homecoming state is verified exact against the origin, and a tampered packet is refused. Inputs: work_dir; optional key. Returns the relay report (births, hops, per-hop errors, homecoming difference). Cost: one job. |
| singularis_compute_in_transitA | Compute on a sealed tower while it travels. Operations: fuse_in_transit (merge knowledge inside the sealed tower), twist_in_transit (transform it into a new sealed tower), energy_audit (report its portal energy). The tower's seal is verified before anything runs; a broken seal is refused and nothing is charged. Inputs: op, tower_in path, tower_out for twist, ridge. Cost: one job per operation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
singularis_mind_merge_v2 and singularis_mind_combine_v2 have byte-for-byte identical descriptions (merge/add/remove/quarantine/shards), making them impossible to tell apart. singularis_fft and singularis_fft2 also overlap, with fft2's own description admitting fft already handles 2D. Several sealed-knowledge-transfer tools (data_carry, knowledge_packs, compute_in_transit, free_universe) share similar 'signed sealed file' concepts, adding further confusion.
All tools use snake_case with a consistent singularis_ prefix, which is highly predictable. The only deviation is the inconsistent _v2 suffix applied to just two of the mind tools while similar tools lack it, and many names are noun-style (balance, gemm, fft, blur) rather than verb_noun, but overall the pattern is coherent.
19 tools is on the heavy side for the apparent scope, and the count is inflated by at least one redundant entry (mind_combine_v2 duplicating mind_merge_v2) plus the overlapping fft2. The account/dispatch/recipe tools plus a broad numerical library are plausible, but the set feels somewhat padded.
The surface covers account lifecycle (register/balance/share), a compress/decompress pair, a solid numerical core (heat, matrix exponential, gemm, fft, blur), and a dispatch/recipes fallback that generalizes to arbitrary jobs, leaving few dead ends. Minor gaps exist around job history or key management, but the catch-all dispatch mitigates most missing operations.