Skip to main content

A comprehensive climate agent for weather forecasts, geocoding, and pollen data

Project description

Oremi Ojọ

Buy me a beer

Oremi Ojọ is a technical service that provides access to weather forecasts, air quality information, pollen levels, and geocoding data. It exposes a comprehensive set of REST API endpoints designed for reliable integration into applications that require environmental and location intelligence. In addition to its REST interface, Oremi Ojọ includes an MCP interface for structured interactions and an agent endpoint that enables natural language queries over its data.

The name "Ojọ" comes from the Yoruba language and means "weather". It reflects the service's purpose of delivering current conditions, forecasts, and related environmental data. Like other services in the Oremi ecosystem—such as Oremi Akọrin and Oremi Isinmi—the name is concise, meaningful, and rooted in Yoruba, reinforcing a consistent identity while remaining easy to recognize and remember.

Oremi Ojọ Logo

Documentation

Find the Oremi Ojọ deployment and API documentation at https://demsking.gitlab.io/oremi-ojo.

Features

  • Weather Forecasts: Retrieve detailed weather information, including temperature, humidity, wind speed, wind direction, sunrise, and sunset times.
  • Air Quality Data: Access air quality metrics such as AQI, PM2.5, PM10, NO₂, and O₃ levels for specific locations.
  • Pollen Data: Get information about pollen levels and types (e.g., grass, birch, olive) to help manage allergies and plan outdoor activities.
  • Geocoding: Perform forward and reverse geocoding to find locations by name, address, or coordinates.
  • Generative Responses: Use natural language queries to retrieve weather, air quality, or pollen data for specific locations.
  • Multilingual Output: Responses are generated directly in the detected (or requested) output language.
  • Multi-Service & Multi-Location Routing: A single query can request weather, air quality, and pollen for one or several places.
  • Structured Pollen Schema: Pollen responses include units, dominant_pollen, and a per-pollen details map with level and severity.
  • Dockerized: Easily deployable using the demsking/oremi-ojo Docker image.

Contribute

Please follow CONTRIBUTING.md.

Versioning

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes,
  • MINOR version when you add functionality in a backwards-compatible manner, and
  • PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

See SemVer.org for more details.

License

Copyright 2026 Sébastien Demanou. All Rights Reserved.

Licensed under the Apache License, Version 2.0. See the LICENSE for the complete license text.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

oremi_ojo-3.0.0b16-py3-none-any.whl (51.2 kB view details)

Uploaded Python 3

File details

Details for the file oremi_ojo-3.0.0b16-py3-none-any.whl.

File metadata

  • Download URL: oremi_ojo-3.0.0b16-py3-none-any.whl
  • Upload date:
  • Size: 51.2 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.13

File hashes

Hashes for oremi_ojo-3.0.0b16-py3-none-any.whl
Algorithm Hash digest
SHA256 8b68f4e101d4f98519d269072de22000ac3ea84cd45cfa03ed5b7f2713142cf8
MD5 32e35dfc28a007586765056613c56c2f
BLAKE2b-256 870f331087e8cdeb9e19e8f3c5022323a1f10dfa5eba11648fd3952e00b49ec7

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page