Integration
Connect Docparser to NREL
When Parsed Document Data Available fires in Docparser, your agent runs Estimate solar energy production in NREL. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Docparser and NREL to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Docparser can start in NREL
When Parsed Document Data Available in Docparser
then Estimate solar energy production in NREL
When Parsed Table Row Available in Docparser
then Find nearest alternative fuel stations in NREL
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Docparser and NREL
Triggers and actions 2 triggers · 7 actions
Trigger
Parsed Document Data AvailableTriggers whenever a new Document is processed and parsed data is available.
Trigger
Parsed Table Row AvailableTriggers whenever a new Document is processed and parsed table rows are available.
Action
Fetch Document From URLFetches a new document from a publicly accessible URL and imports it into Docparser to begin parsing. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
Action
Upload DocumentUploads a new document to Docparser which will immediately begin parsing after reception. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
Action
Estimate solar energy productionEstimates the energy production of a grid-connected photovoltaic system at a location using NREL PVWatts V8, returning annual and monthly AC output, solar radiation and capacity factor.
Action
Find nearest alternative fuel stationsReturns the alternative fuel stations nearest to a given latitude and longitude, ordered by distance, with optional filters such as fuel type, status, access and EV network.
Action
Find utility ratesReturns the annual average residential, commercial and industrial electricity rates ($/kWh) and the local utility company names for a location (2012 data).
Action
Get alternative fuel stationReturns the full details of one alternative fuel station by its station ID.
Action
List alternative fuel stationsReturns alternative fuel stations matching your filters, such as fuel type, state, ZIP code, access, status and EV charging network.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Docparser
Docparser to PrismixReal-time uptime for 77 AI APIs (OpenAI, Anthropic, Cursor, Gemini) — free JSON endpoint, no auth required
Docparser to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Docparser to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Docparser to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Docparser to Google SheetsGoogle Sheets
Docparser to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into NREL
HubSpot to NRELHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to NRELSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to NRELSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to NRELGoogle Sheets
Gmail to NRELGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to NRELGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Docparser and NREL, answered
What can start an automation from Docparser?
Any of Docparser's 2 triggers in the catalog, including Parsed Document Data Available and Parsed Table Row Available. Describe the moment in plain language and your agent picks the right one.
What can your agent do in NREL when something happens in Docparser?
Any of NREL's 5 actions, including Estimate solar energy production, Find nearest alternative fuel stations, Find utility rates and Get alternative fuel station. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from NREL to Docparser?
NREL has no triggers in the catalog today, so automations start in Docparser. If you need the other direction, ask: your agent reads NREL's API documentation and adds it.
Do I have to build a connector for Docparser or NREL?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Docparser and NREL without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.