agentlookups.ai / docs / GreenLight

GreenLight documentation

GreenLight tells you whether plug-in (balcony) solar is legal in the US states it tracks: the law, the power cap, which safety certification a kit needs, and what the law says about telling your utility and about renters and HOAs. Each answer comes with the law's name and dates, a citation, and whether we have checked it against the enacted bill text yet. It works on its website, through an AI assistant over MCP, and as a plain HTTPS API.

What it is and where the data comes from

GreenLight is a registry of enacted state laws on plug-in solar: small solar kits that plug into a regular wall outlet. It records laws that have passed, not bills still in progress.

Cost and access

GreenLight is free during beta. You need no account, no sign-in and no API key. Features, access and pricing may change; see about this beta.

Connect it

Claude (web and desktop)

  1. Open Customize > Connectors, click +, then choose Add custom connector.
  2. Paste https://solar.agentlookups.ai/mcp as the server URL. If it asks for a name, use GreenLight.
  3. Leave Advanced settings (the OAuth fields) empty. GreenLight needs no sign-in. Click Add.
  4. In a chat, click the + button, open Connectors and turn GreenLight on.

On a Team or Enterprise plan, an owner adds the connector first, under Organization settings > Connectors (Add, then Custom, then Web). Members then find it under Customize > Connectors and click Connect. GreenLight is not in Claude's connector directory yet, so add it this way.

Claude Code

claude mcp add --transport http greenlight https://solar.agentlookups.ai/mcp

ChatGPT and other MCP clients

In ChatGPT (OpenAI's steps as of September 2026): turn on Developer mode under Settings > Security and login, open Plugins, click the plus button, and enter https://solar.agentlookups.ai/mcp as the MCP server URL, with no authentication. Whether Developer mode is offered can depend on your account and workspace.

In other clients, add a remote MCP server with the URL https://solar.agentlookups.ai/mcp, transport Streamable HTTP, no authentication. Menu names differ by client. The server keeps no session and replies with plain JSON, not a stream. It takes POST only, one JSON-RPC request per POST, with the headers content-type: application/json and accept: application/json, text/event-stream. To test it by hand:

curl -X POST https://solar.agentlookups.ai/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"solar_law","arguments":{"state":"UT"}}}'

Plain HTTPS API

No MCP needed. This URL returns Utah's record as JSON:

https://solar.agentlookups.ai/v1/state/UT

/v1/states returns every state in the registry. Both give a shorter record than the MCP tool: status, power cap, the law's certification terms (in certification), the law's name and dates, and verification state. For citations, the certification rule in plain words, the utility notice and the renter and HOA fields, use the solar_law tool. /llms.txt sums up the service for AI agents.

The tools

Both tools only read. Neither changes anything.

Example prompts

We ran each of these on September 28, 2026, with the arguments shown. The registry changes as states pass laws and entries are verified, so the tool, not this page, has today's answer.

"Can I use a balcony solar panel in my Utah apartment?"

solar_law with {"state": "UT"}

Came back: Utah's HB 340 is enacted and has applied since May 7, 2025. Verified against the enrolled bill on August 5, 2026, with a link to the official text. Power cap 1,200 W. Any kit certified by an accredited safety lab qualifies, and standard wiring rules apply. No utility notice. The law says nothing about renters or HOAs, so the lease still decides. certification_satisfiable_today was false: no kit that meets the rule can be bought today. The record does not say why.

"Which states' plug-in solar laws has GreenLight checked against the official bill text so far?"

solar_states with no arguments

Came back: eight states, all with enacted laws, each with its law name, power cap and verification state: three verified (New Hampshire, Utah and Vermont) and five under review, plus the honesty rules below. It lists only states in the registry. A state missing from the list says nothing about that state's law.

"I live in Maryland. How big a plug-in solar kit can I use, and do I have to tell my utility?"

solar_law with {"state": "MD"}

Came back: HB 1532 s7-321, power cap 1,200 W. Kits at or under 391 W are exempt from the certification rule; above that, the kit must be lab-certified. Utility notice: "post-install notification". The entry is under review with no official-text link yet, so every field is unconfirmed, and a good answer says so.

"Can I buy a plug-in solar kit that is legal to use in Vermont today?"

solar_law with {"state": "VT"}

Came back: Act 149, verified on August 5, 2026. Only kits certified to UL 3700 or an equivalent qualify, and none exist yet, so nothing qualifies today. Power cap 1,200 W, measured in AC watts. Renters and HOAs: "yes: 10-day tenant notice with deemed approval; covenant override".

"Is plug-in solar legal in Texas?"

solar_law with {"state": "TX"}

Came back: tracked: false, with a note that Texas is not in the registry and that this says nothing about Texas law. A good answer says GreenLight has no record for Texas and does not guess either way.

How to read results

Verification state

Fields in a state record

A solar_law record also carries state, state_name, tracked, verification, verification_note and last_verified. The fields from cap_watts through renter_hoa sit inside provisions.

Certification watch

/watch/state.json holds a verdict and a checked_at time. still-zero means no certified kit yet; found means a possible certification is under review; degraded means the last check had trouble and it reruns daily. In the service's words: "If checked_at is older than ~30h the watch itself is broken and the verdict should not be trusted as current."

The service's honesty rules

Every answer from both tools, except an error message, carries these rules, word for word. An assistant should pass them on:

GreenLight is a registry of enacted state law on plug-in (balcony) solar. Entries start as verification:pending and count as UNDER REVIEW: seeded from research, not yet confirmed field-by-field against the enrolled bill text. verification:verified means that primary-source pass completed on last_verified.

Treat every field of an under-review entry as unconfirmed. Relay the verification status to the user.

This is a record of what the law says as we verified it, never legal advice. Leases, HOA rules, local codes, and utility tariffs can still apply.

An AI-assisted primary-source pass checks law entries against the enrolled bill text; GreenLight's owner approves any correction to a seeded value. No certification claim is published until an independent adversarial verification pass confirms it against the certifying source. The daily UL 3700 watch stamps https://solar.agentlookups.ai/watch/state.json (verdict still-zero | found | degraded).

A state absent from this registry is a statement about the registry, not about that state's law. Do not infer legality or illegality from absence.

Limits

Troubleshooting

Privacy and terms

One privacy page and one set of terms cover all six agentlookups.ai services. In short: no accounts, no cookies, no trackers. A /v1/state/ address names the state (such as /v1/state/UT or /v1/state/Utah), so the state as you typed it lands in the web server's lookup log, which is deleted after 14 days. If you sign up for the certification alert on the website, we keep the email address you typed, and the state if you picked one, until you ask us to delete them. If you unsubscribe, the address stays on a do-not-email list so we never email you again.

GreenLight is run by TopHat Monkey Software LLC.

Last updated: September 28, 2026