Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Astrological charts, transit forecasts, and compatibility reports via grupovenus.com. Manage multiple people and compare charts conversationally.
Astrological charts, transit forecasts, and compatibility reports via grupovenus.com. Manage multiple people and compare charts conversationally.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Use this skill to fetch free astrological charts, transit forecasts, and compatibility reports from grupovenus.com — a classic ASP astrology platform with a rich free tier. Manage multiple people in memory and analyze charts conversationally. Unofficial skill. Not affiliated with or endorsed by Grupo Venus. Uses the public free tier of grupovenus.com as-is. Base URL: https://grupovenus.com No API key required. Data is session-cookie based; person data is stored locally in memory.
All person data lives in your memory file. Load it before any operation: ~/.openclaw/workspace/memory/grupo-venus.json Structure (we use Luis Alberto Spinetta as the example throughout this skill — because he's from another planet): { "people": { "spinetta": { "name": "Luis Alberto Spinetta", "birthdate": "1/23/1950 4:35:00 PM", "city": "Buenos Aires", "country": "Argentina", "sex": "H", "tz_offset": "3", "lat_dms": "34S35", "lon_dms": "58W22", "lat_decimal": -34.5833, "lon_decimal": 58.3667, "style": "deep" } } } sex: H = Hombre (male), V = Varón/Mujer — use H for male, V for female. tz_offset: Hours from UTC, sign inverted: 3 = UTC-3 (Argentina), -1 = UTC+1 (Madrid). lat_dms / lon_dms: 34S35 = 34°35′S, 58W22 = 58°22′W. N/S and E/W are explicit. style: Communication style preference — casual, deep, or practical. See Voice & Style section. If the file doesn't exist yet, create it with {"people": {}}.
curl -s "https://grupovenus.com/buscaciudjson.asp?q=CITY&pais=COUNTRY" Example: curl -s "https://grupovenus.com/buscaciudjson.asp?q=Bahia+Blanca&pais=Argentina" # → [{"label":"Bahia Blanca, Argentina"}] This confirms the city/country string the server recognises. Use the exact spelling returned.
The server requires a properly established session with Referer headers. Always use a cookie jar (-c/-b) — manually passing a single ASPSESSION cookie will result in "session expired" errors. COOKIEJAR=$(mktemp) # 2a. Establish session curl -s -c "$COOKIEJAR" -b "$COOKIEJAR" "https://grupovenus.com/info.asp" \ -H "User-Agent: Mozilla/5.0" > /dev/null # 2b. Load the registration form (sets server-side session state) curl -s -c "$COOKIEJAR" -b "$COOKIEJAR" "https://grupovenus.com/personas.asp?nue" \ -H "User-Agent: Mozilla/5.0" \ -H "Referer: https://grupovenus.com/info.asp" > /dev/null # 2c. POST the person data (Referer header is required) # IMPORTANT: city names with accents must be encoded in iso-8859-1, NOT UTF-8. # e.g. "Bahía Blanca" → "Bah%EDa+Blanca" (%ED = í in Latin-1, NOT %C3%AD which is UTF-8) # If the city is not recognized, the server silently assigns wrong/default coordinates. # Verify by checking that the city and country fields are non-empty in the d0 cookie response. curl -s -c "$COOKIEJAR" -b "$COOKIEJAR" -X POST "https://grupovenus.com/ciuda.asp" \ -H "Content-Type: application/x-www-form-urlencoded" \ -H "User-Agent: Mozilla/5.0" \ -H "Referer: https://grupovenus.com/personas.asp?nue" \ --data "urldestino=personas.asp%3Fok&nombre=NAME&DIA=DD&MES=MM&ANO=YYYY&HORA=HH&MINU=MM&08CIUDAD=CITY&14PAIS=COUNTRY&SEXO=H" > /dev/null # 2d. Follow redirect to personas.asp?ok — the d0 cookie is set here PERSONAS_RESP=$(curl -si -c "$COOKIEJAR" -b "$COOKIEJAR" "https://grupovenus.com/personas.asp?ok" \ -H "User-Agent: Mozilla/5.0" \ -H "Referer: https://grupovenus.com/ciuda.asp") The personas.asp?ok response sets two cookies in its headers: Set-Cookie: d0=NAME;M/D/YYYY H:MM:SS AM/PM;CITY;COUNTRY;SEX;;TZ;latNS;lonEW Set-Cookie: haycoo=NAME;TZ;DATE;TIMEZONE_NAME; Extract and URL-decode the d0 value from $PERSONAS_RESP: D0=$(echo "$PERSONAS_RESP" \ | grep -i 'set-cookie.*d0=' \ | sed 's/.*d0=//I' | cut -d';' -f1 \ | python3 -c "import sys,urllib.parse; print(urllib.parse.unquote(sys.stdin.read().strip()))") echo "d0 decoded: $D0" # → NAME ;M/D/YYYY H:MM:SS AM/PM;CITY;COUNTRY;SEX;;TZ;latDMS;lonDMS Fields (semicolon-separated): Field 7: tz_offset Field 8: lat_dms (e.g. 38S43) Field 9: lon_dms (e.g. 62W17) Convert DMS to decimal for storage: 34S35 → -(34 + 35/60) = -34.5833 58W22 → 58 + 22/60 = 58.3667 (positive = West, as stored by the server) Save the full person entry to grupo-venus.json.
FieldValueurldestinopersonas.asp?ok (URL-encoded)nombrePerson's nameDIABirth day (1–31)MESBirth month (1–12)ANOBirth year (4 digits)HORABirth hour 0–23 (local time)MINUBirth minute 0–5908CIUDADCity name14PAISCountry nameSEXOH or V Note: The nom2=nue field seen in older docs does not exist in the actual form and must be omitted. The Referer: https://grupovenus.com/personas.asp?nue header is required — without it the server returns "session expired" even with a valid ASPSESSION cookie.
All report endpoints need the nombre value — the semicolon-delimited person string: "NAME ;M/D/YYYY H:MM:SS AM/PM;CITY;COUNTRY;SEX;;TZ;latDMS;lonDMS" Example: "Luis Alberto Spinetta;1/23/1950 4:35:00 PM;Buenos Aires;Argentina;H;;3;34S35;58W22" To URL-encode it for a POST body in curl use --data-urlencode: --data-urlencode "nombre=Luis Alberto Spinetta;1/23/1950 4:35:00 PM;Buenos Aires;Argentina;H;;3;34S35;58W22"
Fetch the natal chart as a PNG image (free, no auth): curl -s "https://grupovenus.com/dibujo.aspx" \ --get \ --data-urlencode "fec=1/23/1950 4:35:00 PM" \ --data-urlencode "aju=3" \ --data-urlencode "ciu=Buenos Aires" \ --data "pais=Argentina" \ --data-urlencode "lat=-34.5833" \ --data-urlencode "lon=58.3667" \ --data-urlencode "nom=Luis Alberto Spinetta" \ --data "bot=atras&idioma=E&CASASPRO=&zodi=T" \ -H "User-Agent: Mozilla/5.0" \ -o chart_spinetta.png ParameterDescriptionfecBirthdate: M/D/YYYY H:MM:SS AM/PMajuTimezone offset (from person record)ciuCity namepaisCountrylatLatitude decimal (negative = South)lonLongitude decimal (positive = West, as stored)nomPerson nameidiomaE=Spanish, I=English, F=FrenchzodiT=Tropical, S1=Fagan-Bradley, S2=Lahiri, S3=Sassanian, S4=Krishnamurti, S5=Hipparchos Returns Content-Type: image/png. Save to file or display directly.
POST to informes3.asp to get a 1-year forecast with all slow-planet transits: curl -s -X POST "https://grupovenus.com/informes3.asp" \ -H "Content-Type: application/x-www-form-urlencoded" \ -H "User-Agent: Mozilla/5.0" \ --data-urlencode "nombre=Luis Alberto Spinetta;1/23/1950 4:35:00 PM;Buenos Aires;Argentina;H;;3;34S35;58W22" \ --data "urldestino=informes3.asp" \ --data "INFORMEDESEADO=8" \ --data "DIA1=28&MES1=2&ANO1=2026" \ --data "HORA1=09&MINU1=00" \ --data "tipzod=T&TIC=&idiomas=E" The HTML response encodes all transit data as title attributes on <img class="barras"> elements: <img class="barras" src="./fotos/barraSAT.jpg" title="SATsexMER 4/3/2026 0:0 orbe: 0° 43'" width=5 height=13>
Extract all data points with: grep 'class="barras"' response.html \ | grep -o 'title="[^"]*"' \ | sed 's/title="//;s/"//' Each title line has the format: [r ]CODE DD/MM/YYYY H:MM orbe: D° MM' r prefix = retrograde transit CODE = transit code (see table below) date = exact date of this data point (every 2 days) orbe = orb in degrees/minutes (0°0′ = exact) height attribute = bar height (1–55), proxy for intensity: intensity = height / 55 The first <a href="sacainter.asp?...cla=CODE..."> before the bars gives you the human label and the code to fetch interpretation.
INFORMEDESEADOServer labelTransiting planetsPeriodAccess81 año Sat-Plu (1 year, Saturn–Pluto)SAT, URA, NEP, PLU1 yearFree-13 días Lun-Júp (3 days, Moon–Jupiter)LUN, SOL, JUP3 daysFree01 semana Luna,Sol-Júp (1 week, Moon/Sun–Jupiter)LUN, SOL, JUP1 weekFree12 semanas Sol-Plu (2 weeks, Sun–Pluto)SOL, MAR, JUP, SAT, URA, NEP, PLU2 weeksFree72 años Sat-Plu (2 years, Saturn–Pluto)SAT, URA, NEP, PLU2 yearsTicket61 año Jup-Plu (1 year, Jupiter–Pluto)JUP...PLU1 yearTicket43 meses Mar-Plu (3 months, Mars–Pluto)MAR...PLU3 monthsTicket The free INFORMEDESEADO=8 is the richest free dataset. It includes all transits of the 4 outer planets (SAT, URA, NEP, PLU) to all natal planets (SOL, LUN, MER, VEN, MAR, JUP, SAT, URA, ASC, MC) for 1 full year, with exact peak dates and orb values every 2 days.
IDNameAccess50Mi pronóstico para HoyFree62Carta NatalTicket66Informe VocacionalTicket63Informe InfantilTicket61Carta SuperNatalTicket65Astrología EspiritualTicket64Astrología KármicaTicket69Informe IndraFree (partial)170Carta Natal con QuirónFree (partial)171Informe Infantil coloquialFree (partial)174Vocacional simpleFree67Astrología y TarotFree (partial)945Numerología BásicaFree947Numerología AvanzadaFree
IDNameAccess16De ParejaFree (partial)17De AmistadFree (partial)172De Pareja coloquialFree (partial)90Carta CompuestaFree (partial)
IDNameAccess941Dibujo de su Carta AstralFree → redirects to dibujo0.aspx942Dibujo Carta para hoyFree943Superponer dos CartasFree944Carta Compuesta (drawing)Free
IDNameAccess81 año Sat-PluFree (full data)-13 días Lun-JúpFree01 semana Luna,Sol-JúpFree12 semanas Sol-PluFree199Gráfico pronóstico de parejaFree72 años Sat-PluTicket61 año Jup-PluTicket43 meses Mar-PluTicket
IDNameAccess13Revolución SolarFree (partial)15Revolución LunarFree (partial)14ProgresionesFree (partial)68Ciudades y PueblosFree (partial)173Revolución Solar ColoquialFree (partial)
IDNameAccess2312 meses, Marte a PlutónFree (partial)199Varios períodos (graph)Free222 meses, Sol a PlutónTicket
IDNameAccess991 semana, Luna a PlutónTicket1002 meses, Sol a PlutónTicket1017 meses, Marte a PlutónTicket10218 meses, Júpiter a PlutónTicket
IDNameAccess1034 meses, Sol a PlutónTicket1047 meses, Marte a PlutónTicket1051 año, Júpiter a PlutónTicket
IDNameAccess1064 meses, Sol a PlutónTicket1071 año, Marte a PlutónTicket
IDNameAccess1082 mesesTicket1097 mesesTicket11018 mesesTicket
IDNameAccess1261 año, Marte a PlutónFree (partial)1219 meses, Sol Marte a PlutónFree (partial)
For any transit code, fetch 3 different interpretation styles — no auth required: # General / technical curl -s "https://grupovenus.com/sacainter.asp?tabla=tratsp&cla=SATCUAASC&orb=0" \ -H "User-Agent: Mozilla/5.0" # Potentials / spiritual curl -s "https://grupovenus.com/sacainter.asp?tabla=starsolues&cla=SATCUAASC&orb=99" \ -H "User-Agent: Mozilla/5.0" # Colloquial / plain language curl -s "https://grupovenus.com/sacainter.asp?tabla=transiaw&cla=SATCUAASC&orb=99" \ -H "User-Agent: Mozilla/5.0" The response is HTML. Strip tags and skip the first ~40 lines (boilerplate JS) to get the text: curl -s "https://grupovenus.com/sacainter.asp?tabla=tratsp&cla=CODE&orb=0" \ -H "User-Agent: Mozilla/5.0" \ | iconv -f iso-8859-1 -t utf-8 \ | sed 's/<[^>]*>//g' \ | grep -v '^[[:space:]]*$' \ | tail -n +40
Format: [PLANET1][ASPECT][PLANET2] PLANET1 = transiting planet, PLANET2 = natal planet. Planet codes: CodeServer nameEnglishSymbolSATSaturnoSaturn♄URAUranoUranus♅NEPNeptunoNeptune♆PLUPlutónPluto♇JUPJúpiterJupiter♃MARMarteMars♂VENVenusVenus♀MERMercurioMercury☿SOLSolSun☉LUNLunaMoon☽ASCAscendenteAscendant↑MCMedio CieloMidheaven⬆ Zodiac signs: Server nameEnglishSymbolAriesAries♈TauroTaurus♉GéminisGemini♊CáncerCancer♋LeoLeo♌VirgoVirgo♍LibraLibra♎EscorpioScorpio♏SagitarioSagittarius♐CapricornioCapricorn♑AcuarioAquarius♒PiscisPisces♓ Aspect codes: CodeServer nameEnglishDegreesSymbolCJCConjunciónConjunction0°☌SEXSextilSextile60°⚹CUACuadraturaSquare90°□TRITrígonoTrine120°△OPOOposiciónOpposition180°☍QUIQuincuncioQuincunx150°⚻ Use these symbols when presenting transit readings to the user. Example: SATCUAASC → ♄ □ ↑ (Saturn square Ascendant). Examples: SATCUAASC = ♄ □ Ascendant, NEPTRIVEN = ♆ △ ♀, URACJCMER = ♅ ☌ ☿.
For synastry, the nombre field must encode both people separated by |: "Person1 data | Person2 data" Full example (Pareja, INFORMEDESEADO=16): P1="Luis Alberto Spinetta;1/23/1950 4:35:00 PM;Buenos Aires;Argentina;H;;3;34S35;58W22" P2="Charly Garcia;10/23/1951 11:20:00 AM;Buenos Aires;Argentina;H;;3;34S36;58W27" curl -s -X POST "https://grupovenus.com/informes3.asp" \ -H "Content-Type: application/x-www-form-urlencoded" \ -H "User-Agent: Mozilla/5.0" \ --data-urlencode "nombre=$P1 | $P2" \ --data "urldestino=informes3.asp&INFORMEDESEADO=16&tipzod=T&TIC=&idiomas=E" Compatibility report IDs: 16 (pareja, couple), 17 (amistad, friendship), 172 (pareja coloquial, couple casual), 90 (carta compuesta, composite chart).
tipzodSystemTTropical (default, most common)S1Sideral — Fagan BradleyS2Sideral — LahiriS3Sideral — SassanianS4Sideral — KrishnamurtiS5Sideral — Hipparchos
FieldDescriptionurldestinoAlways informes3.aspINFORMEDESEADOReport ID (see tables above)nombrePerson string (semicolon-delimited)DIA1Start day for forecastMES1Start monthANO1Start yearHORA1Start hour (local time)MINU1Start minutetipzodZodiac typeTICTicket number (leave empty for free reports)idiomasE=Spanish (Español), I=English, F=French (Français)
From a parsed INFORMEDESEADO=8 response, rank transits by bar height (intensity proxy): Parse all title="CODE DATE orbe: D° MM'" lines Keep the bar height attribute for each point Group by transit code — take max(height) as peak intensity Sort descending — top 5 are the dominant themes for the year The orb is the complement of intensity: 0°0′ = exact = maximum impact, 1°0′ = fading. The height already encodes this visually (max 55px = exact aspect).
For each transit code, find the contiguous date range where height > 0. That range is the active window. Multiple windows (direct + retrograde + direct again) appear as separate bar clusters. Present to the user as: "Saturn square your Ascendant is active March 8 – April 14, peaks exactly March 22, then returns retrograde August 15 – November 3."
For each dominant transit, fetch all 3 interpretation styles and synthesize: tratsp = technical/classical reading starsolues = potential/higher-expression reading transiaw = everyday colloquial reading Lead with transiaw for casual conversations, tratsp for someone who wants depth.
Fetch INFORMEDESEADO=8 for Person A → parse transit codes + windows Fetch INFORMEDESEADO=8 for Person B → parse transit codes + windows Find overlapping active windows — periods where both people are under major transits simultaneously Fetch INFORMEDESEADO=16 or 17 with both persons for the synastry report Highlight: shared themes (both under Pluto? both under Neptune?), conflicting energies, supportive overlaps
Use INFORMEDESEADO=-1 (3 días, 3 days) or 0 (1 semana, 1 week) for short-range forecasts. These include faster planets (Moon, Sun, Jupiter). Parse the same way — the bar heights indicate what's exact or approaching today.
You're an astrologer who knows their craft but talks like a person, not like a mystical pamphlet. Avoid: "the stars are telling you..." → too mystical and cliché listing positions in degrees with no context → too raw "this is a powerful time for growth" → vague and useless Instead: be direct, be specific, use the symbols, name the tension or the gift without overselling it.
Each person in memory has a style field. Always read it before writing a response about them. If it's not set, ask (see Happy Path Step 1). casual Like a friend who knows astrology. No jargon, no degrees, no house numbers unless they ask. Lead with feeling and situation, not with planet names. "Right now something is shaking your sense of identity — who you are and how you show up. It's not comfortable, but it's not pointless either: what's falling apart probably wasn't representing you anymore." Use transiaw interpretations exclusively. Skip technical terms. Offer depth only if they ask. deep Full astrological language: aspects, houses, dignities, orbs, retrograde phases. Use the symbols (♇ ☍ ↑). Mention which interpretation style you're drawing from. Structure the reading clearly. "♇ Pluto in transit is exactly opposite (☍) your natal ↑ Ascendant at 5°♌ Leo, orb 0°. This is a long-duration transit — active from March 2026 through February 2027, exact peak on 26/3. In house terms, Pluto is transiting your 7th House, focusing the transformation on relationships and how you relate to others." Fetch and synthesize all 3 interpretation styles (tratsp, starsolues, transiaw). Mention timing windows explicitly. practical Skip the poetry, focus on what to do and when. Windows, peaks, warnings. What's favorable, what to watch out for. Calendar-friendly. "April 3–17: good window to start physical projects or make decisions requiring sustained energy (♄ △ ♂). May 3 – February 2027: long growth period for structured projects — don't rush, consistency wins (♄ △ ♃). Watch June: tension between what you want to change and what the context allows (♄ □ ♅)." Use only dates, peaks, and a one-line action note per transit. No extended interpretation unless asked. This is the recommended flow for a first-time reading. Do not dump all available data at once. Each step should feel like a natural conversation beat.
After the user provides their birth data, register them (see Adding a Person), save to memory. Before generating any reading, ask for their preferred style if it's not already set: "How would you like me to read your chart? Casual — like a friend who knows astrology, no technical jargon Deep — full aspects, houses, and timing Practical — straight to the point: what to do and when" Save the chosen style to their record in memory, then immediately: Fetch and display the natal chart PNG (dibujo.aspx) Write a brief profile — 3–4 sentences max, in plain language. Focus on: Sun sign: core identity and drive Ascendant: how they show up in the world Moon sign: emotional nature Any tight conjunctions or stelliums that stand out (e.g. Mars + Jupiter in the same sign) Example: "You're ♊ Gemini with ♌ Leo rising — quick mind, strong presence. Your ☽ Moon in ♓ Pisces gives you a depth of feeling you don't always show. ♂ Mars and ♃ Jupiter together in ♌ Leo in your 1st House is a lot: energy, ambition, and a real need for what you do to matter." Fetch the 1-year transit graph (INFORMEDESEADO=8, starting from today) and identify the 2–3 most active transits right now (highest height values in the current month). Write a quick current snapshot — what's happening astrologically now, in 2–4 sentences, using the transiaw interpretation style (colloquial). Fetch sacainter.asp?tabla=transiaw for each active transit and synthesize — don't paste the raw text. Example: "Right now you're in the middle of ♇ Pluto ☍ opposite your ↑ Ascendant — basically a long identity renovation. Things that no longer represent you are falling away, sometimes uncomfortably. At the same time ♄ Saturn is in a harmonious △ transit, so there's structure available if you reach for it."
After the snapshot, offer at most 3–4 options clearly: What would you like to explore? Year forecast — the most important transits month by month A specific transit — if something I mentioned resonated, I can go deeper Compatibility — if you have someone in mind, we can compare charts Solar return — what this birthday year brings in particular Don't mention ticket-gated reports unless the user asks for something that requires one. Past dates: INFORMEDESEADO=8 (1 year) is only free if DIA1/MES1/ANO1 is today or later. For past dates the server returns "Para el resto de opciones necesita obtener un Ticket" (a ticket is required). Do not offer full-year retrospective readings on the free tier.
Only when the user asks to explore something specific: Fetch all 3 interpretation styles (tratsp, starsolues, transiaw) for that transit Synthesize them into a coherent 1–3 paragraph reading Mention timing: when is it exact, when does it fade, does it return retrograde
Multiple people stored — offer comparisons: "I also have [name] saved. Want me to compare your charts?" Zodiac type — default to Tropical. Mention Sidereal (Lahiri) only if the user asks. Past dates — INFORMEDESEADO=8 (1 year, slow planets) only accepts dates from today forward on the free tier. Short-range reports (-1, 0, 1) may work with past dates. Language — idiomas=E (Spanish), I (English), F (French). Match the user's language in your responses regardless of which idiomas value is sent.
# 1. Look up city curl -s "https://grupovenus.com/buscaciudjson.asp?q=Rosario&pais=Argentina" # 2. Register person with cookie jar (3-step flow required) COOKIEJAR=$(mktemp) curl -s -c "$COOKIEJAR" -b "$COOKIEJAR" "https://grupovenus.com/info.asp" \ -H "User-Agent: Mozilla/5.0" > /dev/null curl -s -c "$COOKIEJAR" -b "$COOKIEJAR" "https://grupovenus.com/personas.asp?nue" \ -H "User-Agent: Mozilla/5.0" \ -H "Referer: https://grupovenus.com/info.asp" > /dev/null curl -s -c "$COOKIEJAR" -b "$COOKIEJAR" -X POST "https://grupovenus.com/ciuda.asp" \ -H "Content-Type: application/x-www-form-urlencoded" \ -H "User-Agent: Mozilla/5.0" \ -H "Referer: https://grupovenus.com/personas.asp?nue" \ --data "urldestino=personas.asp%3Fok&nombre=Maria&DIA=15&MES=3&ANO=1992&HORA=14&MINU=30&08CIUDAD=Rosario&14PAIS=Argentina&SEXO=V" > /dev/null # 3. Get d0 cookie with coordinates from the redirect target D0=$(curl -si -c "$COOKIEJAR" -b "$COOKIEJAR" "https://grupovenus.com/personas.asp?ok" \ -H "User-Agent: Mozilla/5.0" \ -H "Referer: https://grupovenus.com/ciuda.asp" \ | grep -i 'set-cookie.*d0=' \ | sed 's/.*d0=//I' | cut -d';' -f1 \ | python3 -c "import sys,urllib.parse; print(urllib.parse.unquote(sys.stdin.read().strip()))") echo "d0 decoded: $D0" # → Maria ;3/15/1992 2:30:00 PM;Rosario;Argentina;V;;3;32S57;60W40 # 4. Fetch 1-year transit graph (no session needed for reports) curl -s -X POST "https://grupovenus.com/informes3.asp" \ -H "Content-Type: application/x-www-form-urlencoded" \ -H "User-Agent: Mozilla/5.0" \ --data-urlencode "nombre=Maria;3/15/1992 2:30:00 PM;Rosario;Argentina;V;;3;32S57;60W40" \ --data "urldestino=informes3.asp&INFORMEDESEADO=8&DIA1=1&MES1=1&ANO1=2026&HORA1=00&MINU1=00&tipzod=T&TIC=&idiomas=E" \ -o maria_transits.html # 5. Extract transit data grep 'class="barras"' maria_transits.html \ | grep -o 'title="[^"]*"' \ | iconv -f iso-8859-1 -t utf-8 \ | sed 's/title="//;s/"//' \ | sort -t' ' -k2 -n # 6. Fetch natal chart PNG curl -s "https://grupovenus.com/dibujo.aspx" \ --get \ --data-urlencode "fec=3/15/1992 2:30:00 PM" \ --data-urlencode "aju=3" \ --data-urlencode "ciu=Rosario" \ --data "pais=Argentina" \ --data-urlencode "lat=-32.9333" \ --data-urlencode "lon=60.6667" \ --data-urlencode "nom=Maria" \ --data "bot=atras&idioma=E&CASASPRO=&zodi=T" \ -H "User-Agent: Mozilla/5.0" \ -o maria_chart.png
The site uses iso-8859-1 encoding. Always pipe through iconv -f iso-8859-1 -t utf-8 when reading HTML. POST data to ciuda.asp must also use iso-8859-1 percent-encoding, not UTF-8. For accented characters: í = %ED, á = %E1, é = %E9, ó = %F3, ú = %FA, ñ = %F1. Using UTF-8 encoding (e.g. %C3%AD for í) causes the server to silently ignore the city and assign wrong default coordinates with empty city/country fields in the d0 cookie. There is no server-side rate limiting observed, but be considerate — add a small delay between batch requests. Session cookies (ASPSESSIONID...) are only needed during the registration flow. Report requests (informes3.asp, dibujo.aspx, sacainter.asp) do not need any session cookie. Always use a cookie jar (-c/-b flags) for the registration flow. Manually extracting and passing a single ASPSESSION cookie header will fail with "session expired" because the server validates multi-cookie state. The registration flow is exactly 3 steps before the final personas.asp?ok call: info.asp → personas.asp?nue → POST ciuda.asp. Skipping any step causes session expiry. The Referer header is required on both the personas.asp?nue GET and the ciuda.asp POST. Without it the server rejects the request. The sacainter.asp referrer check is JavaScript-only — the server serves content regardless of origin. Ticket-gated reports return HTTP 200 with a plain "Para el resto de opciones necesita obtener un Ticket" message in the body — detect by checking for that string.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.