Typed request and response clients generated from all 289 OpenAPI operations.
Use VedAstro tools from MCP-compatible assistants while keeping operation identifiers and evidence metadata canonical.
@vedicmatters/client
npm install @vedicmatters/clientimport { VedAstroClient } from "@vedicmatters/client";
const client = new VedAstroClient({
apiKey: process.env.VEDASTRO_API_KEY,
locale: "en",
});
const response = await client.chart.report({
dateTime: "1990-05-15T10:30:00+05:30",
location: { latitude: 28.6139, longitude: 77.209 },
ayanamsa: "LAHIRI",
ruleProfile: "evidence_backed_birth_chart_report_v1",
});vedastro
pip install vedastrofrom vedastro import Client
client = Client(api_key="veda_...", locale="en")
response = client.panchang.day({
"date": "2026-07-15",
"location": {"latitude": 28.6139, "longitude": 77.209},
"timezone": "Asia/Kolkata",
})
print(response.data)vedastro
dart pub add vedastrofinal client = VedAstroClient(
apiKey: 'veda_...',
locale: 'en',
);
final response = await client.prediction.daily<Map<String, Object?>>({
'dateTime': '1990-05-15T10:30:00+05:30',
'location': {'latitude': 28.6139, 'longitude': 77.209},
'ruleProfile': 'evidence_backed_daily_prediction_v1',
});
client.close();Do not embed shared API keys in public browser or mobile applications. Use your own backend-for-frontend, or dashboard JWT flows where supported.
Go, PHP, Ruby, and Java remain planned. Their package names will be published only after contract generation and registry checks are complete.
Production API: https://astroapi.vedicmatters.com. Packages are installable after their approved npm/PyPI/pub.dev publication. Use generated operation IDs for endpoints without a convenience wrapper.