Ecosistema Inmobiliario Homlity

Homlity Real Estate is a WordPress plugin built for the real estate industry. It allows agencies, brokers, and independent agents to create and manage professional property websites quickly and efficiently.
Designed for multi-country and multi-currency operation, it adapts to the needs of real estate professionals across Latin America, Spain, and beyond.
<h3>Key Features</h3>
<ul>
<li>Custom property post type for structured listing management.</li>
<li>Multi-country support with country, city, zone, and neighborhood fields.</li>
<li>Multi-currency support (COP, MXN, EUR, USD, and more).</li>
<li>Fully customizable:
<ul>
<li>Property types (houses, apartments, offices, retail, land, warehouses, etc.).</li>
<li>Operation types (sale, rent, short-term, transfer, etc.).</li>
<li>Custom attributes (bedrooms, bathrooms, parking, area, amenities, etc.).</li>
<li>Property status (available, reserved, sold, rented, etc.).</li>
</ul>
</li>
<li>Agent management: link properties to agents with per-property contact details.</li>
<li>Real estate SEO: clean URLs, metadata-ready structure, and JSON-LD/schema-friendly field layout.</li>
<li>Page builder integrations: Elementor widgets, Divi module, WPBakery, and shortcodes.</li>
<li>Extensible architecture: hooks, filters, and modular structure for ERP and CRM integrations.</li>
</ul>
<h3>About Homlity</h3>
Homlity is a digital ecosystem focused on real estate web solutions, specializing in property website development, custom web applications, and integrations with real estate systems and ERPs.
<h3>Third-Party Libraries</h3>
This plugin bundles the following open-source libraries:
<ul>
<li>GLightbox — MIT License. Lightbox gallery for property photos. 
https://github.com/biati-digital/glightbox</li>
<li>Guzzle HTTP (guzzlehttp/guzzle) — MIT License. HTTP client used for CRM integrations. 
https://github.com/guzzle/guzzle</li>
<li>Guzzle Promises (guzzlehttp/promises) — MIT License. Async promise support for Guzzle. 
https://github.com/guzzle/promises</li>
<li>Guzzle PSR-7 (guzzlehttp/psr7) — MIT License. PSR-7 HTTP message implementation. 
https://github.com/guzzle/psr7</li>
<li>Dompdf (dompdf/dompdf) — LGPL-2.1 License. Generates PDF technical sheets for properties. 
https://github.com/dompdf/dompdf</li>
<li>PHP Font Library (dompdf/php-font-lib) — LGPL-2.1-or-later License. Font handling for Dompdf. 
https://github.com/dompdf/php-font-lib</li>
<li>PHP SVG Library (dompdf/php-svg-lib) — LGPL-3.0-or-later License. SVG rendering for Dompdf. 
https://github.com/dompdf/php-svg-lib</li>
<li>HTML5 PHP (masterminds/html5) — MIT License. HTML5 parser used by Dompdf. 
https://github.com/Masterminds/html5-php</li>
<li>PSR HTTP Client (psr/http-client) — MIT License. HTTP client interface. 
https://github.com/php-fig/http-client</li>
<li>PSR HTTP Factory (psr/http-factory) — MIT License. HTTP factory interface. 
https://github.com/php-fig/http-factory</li>
<li>PSR HTTP Message (psr/http-message) — MIT License. HTTP message interface. 
https://github.com/php-fig/http-message</li>
<li>PHP CSS Parser (sabberworm/php-css-parser) — MIT License. CSS parsing for Dompdf. 
https://github.com/sabberworm/PHP-CSS-Parser</li>
</ul>
All MIT-licensed libraries are GPL-compatible. LGPL-licensed libraries (Dompdf, php-font-lib, php-svg-lib) are used as independent components and are compatible with GPL-2.0-or-later under the LGPL linking exception.
<h3>External Services</h3>
This plugin may connect to the following external services:
<h4>WhatsApp (Meta Platforms, Inc.)</h4>
Used to generate contact links that open a WhatsApp conversation with a property agent, and to generate share links so visitors can send a property listing via WhatsApp. 
* Data sent: The agent’s phone number and an optional pre-filled text message (property title and URL) are included in the link URL. No data is sent to WhatsApp servers unless the visitor clicks the link. 
* When: The link is generated on every property detail page that has an agent with a phone number configured. Data is only transmitted to WhatsApp when the visitor clicks the button. 
* Service provider: Meta Platforms, Inc. 
* Privacy policy: https://www.whatsapp.com/legal/privacy-policy 
* Terms of service: https://www.whatsapp.com/legal/terms-of-service
<h4>Google Maps (Google LLC)</h4>
Used to display an interactive map of the property location, a Street View preview, and a “Get directions” link on property detail pages. 
* Data sent: The property’s geographic coordinates (latitude and longitude) stored by the site administrator. The visitor’s IP address and browser information may be collected by Google when the map or Street View iframe loads. 
* When: Only on property detail pages where geographic coordinates have been saved. The map iframe is loaded automatically when the visitor opens the page. 
* Service provider: Google LLC. 
* Privacy policy: https://policies.google.com/privacy 
* Terms of service: https://developers.google.com/maps/terms-20180207
<h4>YouTube (Google LLC)</h4>
Used to embed property video tours directly on property detail pages. 
* Data sent: The YouTube video ID is included in the iframe URL. The visitor’s IP address and browser information may be collected by YouTube/Google when the iframe loads. 
* When: Only on property detail pages that have a YouTube video URL saved. The iframe is loaded automatically when the visitor opens the page. 
* Service provider: Google LLC. 
* Privacy policy: https://policies.google.com/privacy 
* Terms of service: https://www.youtube.com/t/terms
<h4>OpenStreetMap Nominatim (Geocoding)</h4>
Used to convert property addresses into geographic coordinates (latitude/longitude). 
* Data sent: Street address, neighborhood, city, state/region, and country entered by the site administrator. 
* When: Only when the administrator explicitly clicks the “Geocode” button in the property editor. No data is sent automatically. 
* Service: Nominatim geocoding API, operated by the OpenStreetMap Foundation. 
* Privacy policy: https://osmfoundation.org/wiki/Privacy_Policy 
* Terms of use: https://operations.osmfoundation.org/policies/nominatim/
<h4>CKEditor 5 (CKSource / Mateusz Bukowski Foundation)</h4>
Used to provide a rich-text description editor for property listings inside the WordPress admin dashboard. 
* Data sent: No property or user data is sent to CKEditor’s servers. The browser downloads the CKEditor 5 JavaScript library file from the CDN when an administrator opens the property editor. The download request includes the visitor’s IP address and browser information as standard HTTP headers. 
* When: Only when an administrator opens the property editing screen in wp-admin. End users on the public website are never affected. 
* URL loaded: https://cdn.ckeditor.com/ckeditor5/39.0.1/classic/ckeditor.js 
* Service provider: CKSource Sp. z o.o. (operating as Mateusz Bukowski Foundation). 
* Privacy policy: https://ckeditor.com/legal/privacy-policy/ 
* Terms of service: https://ckeditor.com/legal/ckeditor-oss-license/
<h4>CRM Integrations (Optional)</h4>
When a CRM integration is configured and enabled by the site administrator, the plugin synchronizes property data with external real estate CRM platforms. 
* Data sent: Property details (title, description, price, location, media), agent information. 
* When: Only when the administrator enables and configures a CRM connection. Disabled by default. 
* Note: The specific privacy policy and terms of service depend on the CRM provider configured by the site administrator.
<h4>Analytics / Visit Tracking (Optional)</h4>
The plugin includes optional built-in analytics to count property visits, contact clicks, and PDF downloads. This feature is disabled by default and must be explicitly enabled by the site administrator. 
* Data stored: Anonymized visitor identifier (random cookie), hashed IP address (SHA-256), hashed user-agent string (SHA-256), and event timestamps. All data is stored locally in the WordPress database and is never transmitted to external servers. 
* When: Only when the “Enable Analytics” option is active in the plugin settings. The plugin respects the WP Consent API if a compatible consent plugin is installed. 
* Important: When enabling this feature, site administrators are responsible for obtaining visitor consent in accordance with applicable privacy laws (GDPR, CCPA, etc.) and updating their site’s privacy policy accordingly.

Homlity Real Estate

Real estate plugin to manage property listings, agents, currencies, and multi-country configurations in WordPress.

Kevin Pirnie

AI agents — tools like ChatGPT, Claude, Copilot, and the growing ecosystem of autonomous AI systems — are increasingly being pointed at websites to gather information, interact with APIs, and perform tasks on behalf of users. For a site to work well with these agents, it needs to speak the right language: publishing structured discovery files, declaring its capabilities, and responding to agent-specific requests in the right format.
KP Agent Ready handles all of that for your WordPress site. It implements the current set of agent-readiness standards and the broader AI agent ecosystem — without requiring you to manually create files, edit server configs, or touch a line of code. Everything is managed from a dedicated settings page in the WordPress admin.
<h4>What It Does</h4>
RFC 8288 Link Response Headers 
Every response your site sends will include <code>Link</code> headers pointing agents to your API catalog, agent skills index, and MCP server card. This is how agents find your discovery documents without having to guess URLs.
API Catalog — <code>/.well-known/api-catalog</code> 
Publishes a machine-readable catalog of your site’s APIs in the <code>application/linkset+json</code> format defined by RFC 9727. Each entry in the catalog can point to an OpenAPI specification, human-readable documentation, and a health/status endpoint. If you have not configured any entries yet, the plugin serves a sensible fallback automatically so the endpoint is always valid.
Agent Skills Index — <code>/.well-known/agent-skills/index.json</code> 
Publishes a skills discovery index per the Agent Skills Discovery RFC v0.2.0. This tells agents what your site can do — search your blog, browse your portfolio, submit a contact form, and so on.
Skills are built from three sources:
<ul>
<li>Blog articles — a search skill and a browse skill, toggled with a single switch</li>
<li>Custom post types — any public CPT registered on your site appears as a checkbox; tick it and it gets a browse skill pointing to its archive</li>
<li>Manual entries — define any additional skill with a name, type, description, URL, and an optional sha256 digest</li>
</ul>
MCP Server Card — <code>/.well-known/mcp/server-card.json</code> 
Publishes an MCP Server Card (SEP-1649) identifying your site to Model Context Protocol clients. Configurable name, version, description, transport endpoint, and a capability list. If you do not have an MCP server running yet, just leave the transport blank — the card is still valid and useful for discovery.
OAuth / OIDC Discovery — <code>/.well-known/openid-configuration</code> or <code>/.well-known/oauth-authorization-server</code> 
If your site exposes protected APIs that require authentication, this feature publishes the discovery metadata agents need to authenticate. Supports both OpenID Connect Discovery 1.0 and RFC 8414. Disabled by default — only enable it if you have the infrastructure in place.
OAuth Protected Resource Metadata — <code>/.well-known/oauth-protected-resource</code> 
Complements the OAuth/OIDC feature by publishing RFC 9728 Protected Resource Metadata. Disabled by default.
robots.txt Content Signals 
Appends Content Signals directives to your <code>robots.txt</code> file, declaring your preferences for how AI systems may use your content:
<ul>
<li>ai-train — whether AI companies may use your content to train models</li>
<li>search — whether search engines may index your content</li>
<li>ai-input — whether AI retrieval systems (RAG) may use your content as input</li>
</ul>
Markdown Negotiation 
When an AI agent sends a request with the <code>Accept: text/markdown</code> header, the plugin intercepts the response for singular posts and pages and returns a clean Markdown version of the content. Regular browser requests are completely unaffected.
WebMCP 
Injects a small JavaScript snippet into your page footer that calls <code>navigator.modelContext.provideContext()</code>, exposing your site’s key actions as tools to AI agents running in the browser. Built-in tools include blog search, portfolio navigation, and contact page navigation — each individually toggleable.
llms.txt and llms-full.txt 
Generates physical <code>/llms.txt</code> and <code>/llms-full.txt</code> files in your WordPress web root per the <a href="https://llmstxt.org" rel="nofollow ugc">llmstxt.org</a> specification. These files give AI systems a structured, readable index of your site’s content — who you are, what pages exist, and what your posts are about.
<pre><code>llms.txt contains your site header and a clean list of links by content type. `llms-full.txt` contains the same structure but expands each entry with an excerpt or truncated content block so AI systems can understand the content without fetching every URL.
</code></pre>
Files are regenerated automatically when posts are published, unpublished, or trashed, and whenever settings are saved. A manual Regenerate button is available in the llms.txt settings tab. If your host prevents direct file writes, the generated content is displayed in the admin as a copyable textarea so you can create the files manually.
Configurable options include a custom intro block, toggling pages and posts independently, selecting additional custom post types, setting the excerpt word limit for <code>llms-full.txt</code>, and defining optional additional links that appear under an <code>## Optional</code> section in both files.
<h4>Developer Filters</h4>
Two filters let themes and other plugins extend the plugin’s output without touching settings:
<pre><code>kp_agent_skills — add entries to the agent skills index:

add_filter( 'kp_agent_skills', function ( array $skills ): array {
 $skills[] = [
 'name' => 'my-skill',
 'type' => 'api',
 'description' => 'Does something useful.',
 'url' => 'https://yoursite.com/api/endpoint',
 ];
 return $skills;
} );

kp_webmcp_tools — add tools to the WebMCP context:

add_filter( 'kp_webmcp_tools', function ( array $tools ): array {
 // $tools is the PHP array that becomes the JS tools array
 return $tools;
} );
</code></pre>

KP Agent Ready

Very good for AI

Make your WordPress site discoverable and usable by AI agents via well-known endpoints, MCP, OAuth, and Markdown negotiation.

Homlity Real Estate vs KP Agent Ready