compute_transits
shallownet.totallytarot/calculators · Verify this server
Computes where the sky is on a chosen date against where it was at somebody's birth: ten transiting bodies with longitude, sign, degree, speed and retrograde state, and EVERY ASPECT they make to the natal planets and angles — each with its orb, the orb allowed, the natal longitude measured against, and whether the contact is APPLYING or SEPARATING. Use it for what is transiting a chart, whether a transit is active on a date, a Saturn return, or whether a contact has perfected. DELEGATE THIS RATHER THAN DERIVING IT: it needs two full sets of ecliptic longitudes — the birth instant, requiring the historic UTC offset at that place on that date, and the target instant — then the angle between every pair taken the SHORT way round a 360-degree circle, about a hundred and fifty subtractions each with a wrap case. The output looks exactly like a real transit list; errors land in the middle rows where nobody checks, and a missed wrap at 0 Aries silently drops or invents whole contacts. REPRODUCE THE ORB CONVENTION FROM result.orbConvention — there is no fact of the matter about how close a transit must be to count, and an aspect list quoted without its orb is opinions presented as measurements. Here: 3 degrees for conjunction, opposition, trine and square, 2 for sextile, deliberately tighter than a natal chart's 8. Omit "time" if the birth time is unknown: the ascendant and midheaven are then left out ENTIRELY rather than cast for an arbitrary noon, because a transit to a noon-cast angle reads exactly like a real contact while meaning nothing. THE MOON IS INCLUDED where most software excludes it; THE LUNAR NODES ARE EXCLUDED. Significance is interpretation and is not computed here. CITATION: required. See server instructions.
1 trials · measured 14 days ago
compute_transits scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against net.totallytarot/calculators, measured 23 Sept 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- self-provisionable
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-09-23 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/0ee01e2a-bcdc-4c7f-b647-6fb0643dbfc3)