Skip to content
Ryan Day edited this page May 10, 2017 · 15 revisions

APIs impact on AI Assistant Pilot

Several of the pilot concepts involve using AI Personal Assistants to interact with existing agency Application Programming Interfaces (APIs). This makes "wrapping" an existing API with the AI Personal Assistant one of the critical use cases for the pilot, and useful to have a specific page on it for ease of access during the pilot. (Yes we are aware that "APIs through IPAs" is going to be confusing!)

This page contains information related to using public APIs with AI Personal Assistants so that the technical POCs for each company can assist with this specific issue.

Representative User Story

As: an API owner

I want to: make my APIs available through AI Personal Assistants

So that: the Public can interact with my existing public API through new channels

Questions and Answers

  • Q: What is the quickest path to expose an existing REST API on each API Personal Assistant?
  • A:

List of APIs in Pilot

The following pilot concepts include existing APIs that need to be exposed through this project:

AIDS.gov

HUD

  • numerous APIs available via the website egis.hud.gov

DOL

DOT

Library of Medicine

  • MedlinePlus offers developers programmatic access to data/content via XML

NPS

NOAA

Recreation.gov

DoS

USAGov

Technical Links for Each AI Personal Assistant

(In this section, technical POCs for the AI Personal Assistants can share the best technical links related to this use case.)

AI Personal Assistant #1

  • link to reference docs

AI Personal Assistant #2

  • link to reference docs
  • ToDo: Fill out Concept Pages for: DHS, FBI, TSA, USPS
  • ToDo: Merge HHS and HHS Ofc. Nactional Coordinator pages
  • ToDo: Update Problem Statement, or delete it if the relevant text is in other pages
  • ToDo: Update Project Hypothesis, or delete it if the relevant text is in other pages
Clone this wiki locally